LARTC: trace control for netem

Hi Stephen

As discussed yesterday, here our patches to integrate trace control into netem

Trace Control for Netem: Emulate network properties such as long range dependency and self-similarity of cross-traffic.

A new option (trace) has been added to the netem command. If the trace option is used, the values for packet delay etc. are read from a pregenerated trace file, afterwards the packets are processed by the normal netem functions. The packet action values are readout from the trace file in user space and sent to kernel space via configfs.

_______________________________________________
Netem mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/netem

Hi Stephen

As discussed yesterday, here our patches to integrate trace control into netem

Trace Control for Netem: Emulate network properties such as long range dependency and self-similarity of cross-traffic.

A new option (trace) has been added to the netem command. If the trace option is used, the values for packet delay etc. are read from a pregenerated trace file, afterwards the packets are processed by the normal netem functions. The packet action values are readout from the trace file in user space and sent to kernel space via configfs.

_______________________________________________
Netem mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/netem

Hi Stephen

As discussed yesterday, here our patches to integrate trace control into netem

Trace Control for Netem: Emulate network properties such as long range dependency and self-similarity of cross-traffic.

A new option (trace) has been added to the netem command. If the trace option is used, the values for packet delay etc. are read from a pregenerated trace file, afterwards the packets are processed by the normal netem functions. The packet action values are readout from the trace file in user space and sent to kernel space via configfs.

_______________________________________________
Netem mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/netem

Hi Stephen

I just wanted to ask you, if you already had time to test our trace extension for netem as discussed on the 13th of December.

Cheers
Rainer

Quoted 11 lines · Rainer Baumann

Hi Stephen

As discussed yesterday, here our patches to integrate trace control into netem

Trace Control for Netem: Emulate network properties such as long range dependency and self-similarity of cross-traffic.

A new option (trace) has been added to the netem command. If the trace option is used, the values for packet delay etc. are read from a pregenerated trace file, afterwards the packets are processed by the normal netem functions. The packet action values are readout from the trace file in user space and sent to kernel space via configfs.

Quoted 18 lines · On Wed, 07 Feb 2007 19:36:22 +0100 Rainer Baumann <[email protected]>…

Hi Stephen

I just wanted to ask you, if you already had time to test our trace extension for netem as discussed on the 13th of December.

Cheers
Rainer

Quoted 8 lines · Rainer Baumann

Hi Stephen

As discussed yesterday, here our patches to integrate trace control into netem

Trace Control for Netem: Emulate network properties such as long range dependency and self-similarity of cross-traffic.

Quoted 4 lines

Quoted 4 lines

A new option (trace) has been added to the netem command. If the trace option is used, the values for packet delay etc. are read from a pregenerated trace file, afterwards the packets are processed by the normal netem functions. The packet action values are readout from the trace file in user space and sent to kernel space via configfs.

I looked at it some more, and want to go in and clean the configuration and buffer interface slightly before inclusion. Once it is in I get stuck with the ABI so don't want to do something wrong.