From: Rainer Baumann <baumann@tik.ee.ethz.ch>
To: Stephen Hemminger <shemminger@osdl.org>, netdev@VGER.KERNEL.ORG
Subject: [PATCH 2.6.16.19 2/2] LARTC: trace control for netem: kernelspace
Date: Wed, 02 Aug 2006 19:21:56 +0200 [thread overview]
Message-ID: <44D0DF34.4020405@tik.ee.ethz.ch> (raw)
Trace Control for Netem: Emulate network properties such as
long-dependency and self-similarity of cross-traffic.
The delay, drop, duplication and corruption values are readout in user
space and sent to kernel space via procfs.
The kernel determines the time when new values should be sent by the use
of SIGSTOP and SIGCONT signals.
In order to have always packet action values ready to apply, there are
two buffers that hold these values.
Packet action values can be read from one buffer and the other buffer
can be refilled with new values simultaneously.
If a buffer is empty it will be switched to the other buffer and a
SIGCONT signal is sent in order to receive new packet action values.
Having applied the delay value to a packet, the packet gets processed by
the original netem functions.
Signed-off-by: Rainer Baumann <baumann@tik.ee.ethz.ch>
---
Patch for linux kernel 2.6.16.19: http://tcn.hypert.net/tcnKernel.patch
next reply other threads:[~2006-08-02 17:21 UTC|newest]
Thread overview: 5+ 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 2/2] LARTC: trace control for netem: kernelspace Rainer Baumann
2006-09-22 6:15 Rainer Baumann
2006-09-22 15:19 ` Hagen Paul Pfeifer
2006-09-22 17:20 ` Stephen Hemminger
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=44D0DF34.4020405@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).