From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Rainer Baumann <baumann@tik.ee.ethz.ch>
Cc: netdev@VGER.KERNEL.ORG, netem@linux-foundation.org
Subject: Re: [Netem] [Fwd: [PATCH 2.6.18 0/2] LARTC: trace control for netem]
Date: Tue, 13 Feb 2007 16:16:02 -0800 [thread overview]
Message-ID: <20070213161602.16607203@freekitty> (raw)
In-Reply-To: <45CA1C26.1080405@tik.ee.ethz.ch>
On Wed, 07 Feb 2007 19:36:22 +0100
Rainer Baumann <baumann@tik.ee.ethz.ch> wrote:
> Hi Stephen
>
> I just wanted to ask you, if you already had time to test our trace
> extension for netem as discussed on the 13th of December.
>
> Cheers
> Rainer
>
> Rainer Baumann wrote:
> > Hi Stephen
> >
> > As discussed yesterday, here our patches to integrate trace control into netem
> >
> >
> >
> > 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.
> >
> >
>
I looked at it some more, and want to go in and clean the configuration and buffer interface
slightly before inclusion. Once it is in I get stuck with the ABI so don't want to do something
wrong.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-02-14 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 10:39 [PATCH 2.6.18 0/2] LARTC: trace control for netem Rainer Baumann
2006-12-29 14:27 ` [Fwd: [Netem] [PATCH 2.6.18 0/2] LARTC: trace control for netem] Rainer Baumann
2007-01-14 21:40 ` Rainer Baumann
2007-02-07 18:36 ` Rainer Baumann
2007-02-14 0:16 ` Stephen Hemminger [this message]
2007-02-14 8:57 ` [Netem] [Fwd: " 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=20070213161602.16607203@freekitty \
--to=shemminger@linux-foundation.org \
--cc=baumann@tik.ee.ethz.ch \
--cc=netdev@VGER.KERNEL.ORG \
--cc=netem@linux-foundation.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).