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.17.13 0/2] LARTC: trace control for netem
Date: Sat, 23 Sep 2006 09:04:45 +0200 [thread overview]
Message-ID: <4514DC8D.2010405@tik.ee.ethz.ch> (raw)
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.
Sorry, yesterday, this was the old version, this here is now the new version!
After our patches from 2nd and 22th of August we have integrated the comments from Stephen and hope we are on the right way now.
We are looking forward for any comments, feedback and suggestions!
reply other threads:[~2006-09-23 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4514DC8D.2010405@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).