From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [RFC] netem - add jitter support.
Date: Fri, 9 Jul 2004 16:53:14 -0700 [thread overview]
Message-ID: <20040709165314.485cdc52.davem@redhat.com> (raw)
In-Reply-To: <20040708135320.03366bd7@dell_ss3.pdx.osdl.net>
On Thu, 8 Jul 2004 13:53:20 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> This patch adds jitter if desired to the delayed packets in the
> netem scheduler. I dropped the rate stuff out and reorganized so
> that an underlying pfifo queue is used (next plan is to make it
> have class ops).
>
> The jitter is given as sigma to a Gaussian normal distribution. The actual
> implementation is a reduced form of the table driven stuff in NISTnet
> (free).
I'm going to apply this. Stephen please send me
a 2.4.x version as well.
Thanks.
prev parent reply other threads:[~2004-07-09 23:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 20:53 [RFC] netem - add jitter support Stephen Hemminger
2004-07-09 1:14 ` jamal
2004-07-09 23:49 ` David S. Miller
2004-07-12 15:12 ` Stephen Hemminger
2004-07-13 2:39 ` jamal
2004-07-13 3:03 ` Weiguang Shi
2004-07-13 3:36 ` shemminger
2004-07-13 10:42 ` jamal
2004-07-09 23:53 ` David S. Miller [this message]
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=20040709165314.485cdc52.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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).