All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Salsano <stefano.salsano@uniroma2.it>
To: David Miller <davem@davemloft.net>
Cc: shemminger@vyatta.com, fabio.ludovici@yahoo.it, netdev@vger.kernel.org
Subject: Re: [PATCH] netem/iproute2 solving correlated loss issues [2/5]
Date: Sat, 19 Dec 2009 10:48:29 +0100	[thread overview]
Message-ID: <4B2CA16D.4090801@uniroma2.it> (raw)
In-Reply-To: <20091218.200158.112585402.davem@davemloft.net>

David Miller wrote:
> I would like some kind of commit message which at least
> explains what in the world this stuff is, how it works,
> why we want it etc.
> 

you're right we will put this information in the commit messages, some 
hints hereafter:

starting from the consideration that the model for generating correlated 
loss is broken in current netem (as for example described in
https://lists.linux-foundation.org/pipermail/netem/2007-September/001156.html)
we have implemented a more general loss model

the patch allows to generate loss patterns according to a determinist 
pattern that can be given as input:

tc qdisc add/change dev eth0 root netem loss_pattern filename

or according to different loss models including the ones commonly used 
in the literature (bernoulli, gilbert, gilbert-elliot...)

tc qdisc add/change dev eth0 root netem loss_bern       p
tc qdisc add/change dev eth0 root netem loss_gilb       p r [1-h]
tc qdisc add/change dev eth0 root netem loss_gilbell    p r [1-h [1-k]]
tc qdisc add/change dev eth0 root netem loss_GI         ploss 
[burst_length [density [pisol [good_burst_length]]]]
tc qdisc add/change dev eth0 root netem loss_GI_tran    p13 p31 [p32 p23 
[p14]]
tc qdisc add/change dev eth0 root netem loss_gilb_4s    p r [1-h]
tc qdisc add/change dev eth0 root netem loss_gilbell_4s p r [1-h [1-k]]

(full explanation is reported in 
http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetEm2)


-- 
*******************************************************************
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
*******************************************************************

  reply	other threads:[~2009-12-19  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B2B5A26.8050400@uniroma2.it>
2009-12-18 11:24 ` [PATCH] netem/iproute2 solving correlated loss issues [2/5] Fabio Ludovici
2009-12-18 17:36   ` Stephen Hemminger
2009-12-18 23:49     ` Stefano Salsano
2009-12-19  4:01     ` David Miller
2009-12-19  9:48       ` Stefano Salsano [this message]
2009-12-18 11:27 ` [PATCH] netem/iproute2 solving correlated loss issues [3/5] Fabio Ludovici
2009-12-18 11:30 ` [PATCH] netem/iproute2 solving correlated loss issues [4/5] Fabio Ludovici
     [not found] ` <4B2B5A65.1060300@uniroma2.it>
2009-12-18 11:30   ` [PATCH] netem/iproute2 solving correlated loss issues [5/5] Fabio Ludovici

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=4B2CA16D.4090801@uniroma2.it \
    --to=stefano.salsano@uniroma2.it \
    --cc=davem@davemloft.net \
    --cc=fabio.ludovici@yahoo.it \
    --cc=netdev@vger.kernel.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.