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 2/2] LARTC: trace control for netem: kernelspace
Date: Sat, 23 Sep 2006 09:04:58 +0200 [thread overview]
Message-ID: <4514DC9A.2000505@tik.ee.ethz.ch> (raw)
Trace Control for Netem: Emulate network properties such as long range dependency and self-similarity of cross-traffic.
kernel space:
The delay, drop, duplication and corruption values are readout in user space and sent to kernel space via configfs. The userspace process will "hang on write" until the kernel needs new data.
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. The synchronization of "need more delay values" and "return from write" is done with the use of wait queues.
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.17.13: http://tcn.hypert.net/tcn_kernel_configfs.patch
next reply other threads:[~2006-09-23 7:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 7:04 Rainer Baumann [this message]
2006-09-25 20:28 ` [PATCH 2.6.17.13 2/2] LARTC: trace control for netem: kernelspace Stephen Hemminger
2006-09-26 20:17 ` Rainer Baumann
2006-09-26 20:45 ` Stephen Hemminger
2006-09-26 21:03 ` David Miller
2006-12-09 9:17 ` Rainer Baumann
2006-12-13 18:16 ` Stephen Hemminger
2007-01-20 9:05 ` TCN im Kern Rainer Baumann
2007-01-20 22:18 ` 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=4514DC9A.2000505@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).