From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Stefano Salsano <stefano.salsano@uniroma2.it>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
David Miller <davem@davemloft.net>,
Fabio Ludovici <fabio.ludovici@yahoo.it>,
netdev@vger.kernel.org, netem@lists.linuxfoundation.org
Subject: Re: [RFC] netem: correlated loss generation (v3)
Date: Thu, 20 May 2010 01:04:33 +0200 [thread overview]
Message-ID: <20100519230433.GE5146@nuttenaction> (raw)
In-Reply-To: <4BF46B90.1000806@uniroma2.it>
* Stefano Salsano | 2010-05-20 00:52:00 [+0200]:
>So my opinion is that the need to emulate "correlated" loss patterns
>is not academic, but it is a real need from industry... of course we
>can debate if it is a "niche" requirement or not
netem is not in the processing hot path, so there is no issue to add an
additional component. If there are some[TM] users and it is usable, I am
fine with this patch!
>tc qdisc change dev wlan0 root netem loss 2 10
>
>because this produces broken results...
How to model this specific network characteristic (2% loss, correlation 10%)
with your modifications? Can you give us an example?
Cheers, Hagen
--
Hagen Paul Pfeifer <hagen@jauu.net> || http://jauu.net/
Telephone: +49 174 5455209 || Key Id: 0x98350C22
Key Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22
next prev parent reply other threads:[~2010-05-19 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BD84428.30904@uniroma2.it>
2010-05-18 3:56 ` [RFC] netem: correlated loss generation (v3) Stephen Hemminger
2010-05-18 5:19 ` Eric Dumazet
2010-05-19 21:42 ` Hagen Paul Pfeifer
2010-05-19 22:52 ` Stefano Salsano
2010-05-19 23:04 ` Hagen Paul Pfeifer [this message]
2010-05-20 0:17 ` Stephen Hemminger
2010-05-20 0:43 ` Hagen Paul Pfeifer
2010-05-20 0:22 ` Stefano Salsano
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=20100519230433.GE5146@nuttenaction \
--to=hagen@jauu.net \
--cc=davem@davemloft.net \
--cc=fabio.ludovici@yahoo.it \
--cc=netdev@vger.kernel.org \
--cc=netem@lists.linuxfoundation.org \
--cc=shemminger@vyatta.com \
--cc=stefano.salsano@uniroma2.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.