From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Stefano Salsano <stefano.salsano@uniroma2.it>,
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 02:43:30 +0200 [thread overview]
Message-ID: <20100520004330.GF5146@nuttenaction> (raw)
In-Reply-To: <20100519171733.71c24539@nehalam>
* Stephen Hemminger | 2010-05-19 17:17:33 [-0700]:
>The old model was useful, but it really didn't do correlated loss.
>For legacy, the old syntax will go through the same code and generate
>the same result.
Is this really necessary? The right thing is to fix the broken behavior! If
the new patch provides this, great. Imaging a network analysis for a PhD
dissertation based on a broken correlation algorithm - the whole results are
misleading and wrong. No one deserves this ... ;-)
If the current algorithm is broken then the mechanism must be fixed. Preserve
compatibility is counterproductive in this case.
>tc qdisc change dev eth0 root netem
> loss 2 10 # compat syntax
> loss random 2 10 # same as above
> loss deterministic file # loss model based on bitmap
> loss state p13 [p31 [p32 [p23 [p14]]]] # 4 state
> loss model p [r [1-h [1-k]]] # gilbert elliot model
>
>Any suggestions for better syntax are appreciated.
Not at the moment, looks clear and understandable.
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-20 0:43 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
2010-05-20 0:17 ` Stephen Hemminger
2010-05-20 0:43 ` Hagen Paul Pfeifer [this message]
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=20100520004330.GF5146@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 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).