From: Stefano Salsano <stefano.salsano@uniroma2.it>
To: Hagen Paul Pfeifer <hagen@jauu.net>
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 00:52:00 +0200 [thread overview]
Message-ID: <4BF46B90.1000806@uniroma2.it> (raw)
In-Reply-To: <20100519214239.GD5146@nuttenaction>
Hagen Paul Pfeifer wrote:
> * Stephen Hemminger | 2010-05-17 20:56:21 [-0700]:
>
> Why mainline? I questioning the advantage for the big audience, it looks like
> a academic only piece of software - correct me if I'm wrong.
>
as an author, I can only give a "biased" point of view... anyway our
work started from a cooperation with an industry which needed to test
its solutions for fax/modem over IP under correlated loss. When we put
our first version on the netem list, we were asked by people from
another industry to add the feature of loss patterns coming out from a
deterministic table.
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
> The authors pointed to some weak points in the implementation of the current
> loss/correlation logic. But this "fix", add another - complicated component -
> and let the broken components untouched ...
Leaving or removing the broken component is an independent issue.
May be we should allow to use the old syntax like this:
tc qdisc change dev wlan0 root netem loss 2
because it was working OK, and we should disallow to use the old model
in this way:
tc qdisc change dev wlan0 root netem loss 2 10
because this produces broken results...
BR,
Stefano
>
> HGN
>
--
*******************************************************************
Stefano Salsano
Dipartimento Ingegneria Elettronica
Universita' di Roma "Tor Vergata"
Via del Politecnico, 1 - 00133 Roma - ITALY
http://netgroup.uniroma2.it/Stefano_Salsano/
E-mail : stefano.salsano@uniroma2.it
Cell. : +39 320 4307310
Office : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
*******************************************************************
next prev parent reply other threads:[~2010-05-19 23:12 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 [this message]
2010-05-19 23:04 ` Hagen Paul Pfeifer
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=4BF46B90.1000806@uniroma2.it \
--to=stefano.salsano@uniroma2.it \
--cc=davem@davemloft.net \
--cc=fabio.ludovici@yahoo.it \
--cc=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=netem@lists.linuxfoundation.org \
--cc=shemminger@vyatta.com \
/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.