[PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace

[PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace

[Rainer Baumann]

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

The directory tc/netem was split in two parts, one containing the
original distributions and the other the tools to generate trace files
as well as the program responsible for reading the delay values from the
trace file and sending them to the kernel (called flowseed).
If the trace option is set, netem starts the flowseedprocess and
initializes the kernel. To be able to kill the flowseedprocess, in case
the command was faulty, the PID of the flowseedprocess is passed to the
netem kernel module. If the kernel receives packet delay data from a not
registered PID, the Process will be killed. The flowseedprocess does not
send data to the kernel until the registration is completed.

Signed-off-by: Rainer Baumann <baumann@tik.ee.ethz.ch>

---

Patch for iproute2-2.6.16-060323: http://tcn.hypert.net/tcnIproute.patch

[PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace

[Rainer Baumann]

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

The directory tc/netem was split in two parts, one containing the
original distributions and the other the tools to generate trace files
as well as the program responsible for reading the delay values from the
trace file and sending them to the kernel (called flowseed).
If the trace option is set, netem starts the flowseedprocess and
initializes the kernel. To be able to kill the flowseedprocess, in case
the command was faulty, the PID of the flowseedprocess is passed to the
netem kernel module. If the kernel receives packet delay data from a not
registered PID, the Process will be killed. The flowseedprocess does not
send data to the kernel until the registration is completed.

Signed-off-by: Rainer Baumann <baumann@tik.ee.ethz.ch>

---

Patch for iproute2-2.6.16-060323: http://tcn.hypert.net/tcnIproute.patch

[PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace

[Rainer Baumann]

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

user space (iproute2):
The directory tc/netem was split in two parts, one containing the original distribution tables and the other the tools to generate trace files as well as the program responsible for reading the delay values from the trace file and sending them to the kernel (called flowseed).

If the trace option is set, netem initializes the kernel and starts the flowseedprocess. The flowseedprocess does not
send data to the kernel until the registration is completed. The data is sent to the kernel module via configfs. For each qdisc applied, a new directory (in /config/tcn/) is created. The write returns when the kernel needs new data, or when the corresponding qdisc was deleted. In the first case new data is sent and in the latter case the flowseedprocess terminates himself.

Signed-off-by: Rainer Baumann <baumann@tik.ee.ethz.ch>

---

Patch for iproute2-2.6.16-060323: http://tcn.hypert.net/tcn_iproute2.patch