[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100519171733.71c24539@nehalam>
Date: Wed, 19 May 2010 17:17:33 -0700
From: Stephen Hemminger <shemminger@...tta.com>
To: Hagen Paul Pfeifer <hagen@...u.net>
Cc: Stefano Salsano <stefano.salsano@...roma2.it>,
David Miller <davem@...emloft.net>,
Fabio Ludovici <fabio.ludovici@...oo.it>,
netdev@...r.kernel.org, netem@...ts.linuxfoundation.org
Subject: Re: [RFC] netem: correlated loss generation (v3)
On Thu, 20 May 2010 01:04:33 +0200
Hagen Paul Pfeifer <hagen@...u.net> wrote:
> * 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?
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.
iproute2 syntax is not finalized but, plan is simplified version of
the NetemCLG paper.
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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists