From: Rainer Baumann <baumann@tik.ee.ethz.ch>
To: Stephen Hemminger <shemminger@osdl.org>,
netdev@VGER.KERNEL.ORG, netem@osdl.org
Subject: [PATCH 2.6.16.19 1/2] LARTC: trace control for netem: userspace
Date: Fri, 22 Sep 2006 08:13:54 +0200 [thread overview]
Message-ID: <45137F22.4000304@tik.ee.ethz.ch> (raw)
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
next reply other threads:[~2006-09-22 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 6:13 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-08-02 17:21 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=45137F22.4000304@tik.ee.ethz.ch \
--to=baumann@tik.ee.ethz.ch \
--cc=netdev@VGER.KERNEL.ORG \
--cc=netem@osdl.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).