netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rainer Baumann <baumann@tik.ee.ethz.ch>
To: Stephen Hemminger <shemminger@osdl.org>, netdev@VGER.KERNEL.ORG
Subject: [PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace
Date: Wed, 02 Aug 2006 19:21:43 +0200	[thread overview]
Message-ID: <44D0DF27.5000403@tik.ee.ethz.ch> (raw)

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




             reply	other threads:[~2006-08-02 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 17:21 Rainer Baumann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-22 14:32 [PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace Rainer Baumann
2006-09-22  6:13 Rainer Baumann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44D0DF27.5000403@tik.ee.ethz.ch \
    --to=baumann@tik.ee.ethz.ch \
    --cc=netdev@VGER.KERNEL.ORG \
    --cc=shemminger@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).