From: Rainer Baumann <baumann@tik.ee.ethz.ch>
To: Stephen Hemminger <shemminger@osdl.org>, netdev@VGER.KERNEL.ORG
Subject: [PATCH 2.6.16.19 0/2] LARTC: trace control for netem
Date: Wed, 02 Aug 2006 19:21:27 +0200 [thread overview]
Message-ID: <44D0DF17.6060809@tik.ee.ethz.ch> (raw)
Hi,
We developed an extension to the network emulator netem, that provides
emulation of long term network properties such as long-range dependence
and self-similarity of cross-traffic. It is not possible to emulate
these properties with the statistical tables for the packet delay
values used by the original netem.
We read the values for the packet delay, drop, loss and corruption from
a pre-generated trace file. This trace file is obtained by monitoring
network traffic and writing all actions to a trace file. During the
emulation the packets get processed according the values in such a trace
file. Detailed information are available on our
Webseitehttp://tcn.hypert.net
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 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 procfs.
The evaluation results show similar behavior for our enhancement and the
original netem with respect to packet delay precision and packet loss at
high load (e.g. 80'000 packets per second).
It is possible to add, change or delete multiple netem qdiscs on-the-fly
(original netem qdiscs and trace qdiscs mixed).
We are looking forward for any comments, feedback and suggestions!
Thanks,
Rainer
next reply other threads:[~2006-08-02 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 17:21 Rainer Baumann [this message]
2006-08-02 18:19 ` [PATCH 2.6.16.19 0/2] LARTC: trace control for netem Stephen Hemminger
2006-08-02 19:02 ` Rainer Baumann
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 14:32 Rainer Baumann
2006-08-22 21:37 ` Stephen Hemminger
2006-09-22 6:12 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=44D0DF17.6060809@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).