From: Ariane Keller <ariane.keller@tik.ee.ethz.ch>
To: netdev@vger.kernel.org
Cc: shemminger@linux-foundation.org, herbert@gondor.apana.org.au,
Rainer Baumann <baumann@tik.ee.ethz.ch>
Subject: Re: [PATCH 0/2] netem: trace enhancement
Date: Tue, 27 Nov 2007 14:57:26 +0100 [thread overview]
Message-ID: <474C2246.50205@ee.ethz.ch> (raw)
In-Reply-To: <20071120231131.oqn4s5eda84k4csw@email.ee.ethz.ch>
I just wanted to ask whether there is a general interest in this patch.
If yes: great, how to proceed?
otherwise: please let me know why.
Thanks!
Ariane Keller wrote:
> Hi Stephen
>
> Approximately a year ago we discussed an enhancement to netem,
> which we called "trace control for netem".
>
> We obtain the value for the packet delay, drop, duplication and
> corruption from a so called "trace file". The trace file may be obtained
> by monitoring network traffic and thus enables us to emulate "real
> world" network behavior.
>
> Traces can ether be generated individually (we supply a set of tools to
> do this) or can be downloaded from our homepage: http://tcn.hypert.net .
>
> Since our last submission on 2006-12-15 we did some code clean up and
> have created two new patches one against kernel 2.6.23.8 and one against
> iproute2-2.6.23.
> To refer to our discussion from last year please have a look at messages
> with subject "LARTC: trace control for netem".
>
> We are looking forward for any comments, suggestions and instructions to
> bring the trace enhancement to the kernel and to iproute2.
>
> Thanks,
> Ariane
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-27 13:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 22:11 [PATCH 0/2] netem: trace enhancement Ariane Keller
2007-11-27 13:57 ` Ariane Keller [this message]
2007-11-29 21:45 ` Stephen Hemminger
2007-11-29 22:03 ` Patrick McHardy
2007-11-30 16:25 ` Ariane Keller
2007-12-03 7:45 ` Patrick McHardy
2007-12-03 9:12 ` Ariane Keller
2007-12-03 17:35 ` Patrick McHardy
2007-12-03 18:29 ` Ben Greear
2007-12-04 14:45 ` Ariane Keller
2007-12-04 14:58 ` Patrick McHardy
2007-12-05 12:57 ` Ariane Keller
2007-12-05 13:05 ` Patrick McHardy
2007-12-10 14:32 ` Ariane Keller
2007-12-12 23:13 ` Stephen Hemminger
2007-12-04 17:40 ` Ben Greear
2007-12-04 17:54 ` Ariane Keller
2007-12-04 18:07 ` Ben Greear
2007-12-04 21:41 ` Ariane Keller
2007-12-04 22:21 ` Ben Greear
2007-12-05 6:12 ` Ariane Keller
2007-12-23 19:54 ` Ariane Keller
2007-12-23 19:54 ` [PATCH 0/2] netem: trace enhancement: kernel Ariane Keller
2007-12-28 16:08 ` Patrick McHardy
2007-12-28 21:02 ` Ariane Keller
2007-12-23 19:54 ` [PATCH 0/2] netem: trace enhancement: iproute Ariane Keller
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=474C2246.50205@ee.ethz.ch \
--to=ariane.keller@tik.ee.ethz.ch \
--cc=baumann@tik.ee.ethz.ch \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=shemminger@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).