All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [RFC] netem - enhancement
Date: Wed, 18 Aug 2004 14:16:00 -0700	[thread overview]
Message-ID: <20040818141600.1fd67e91.davem@redhat.com> (raw)
In-Reply-To: <20040811123103.620c2a36@dell_ss3.pdx.osdl.net>

On Wed, 11 Aug 2004 12:31:03 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:

> This still needs more testing to go into the mainstream but here is the
> updated version of netem.  It adds:
>   * distribution table (if any) loaded as part of the configuration
>   * random packet duplication
>   * correlated random number's for loss, jitter, duplication
>   * changing netem parameters doesn't wipe out underlying qdisc
>   * better random number generator - simple net_random just isn't good enough
> 
> Also more complete comments and attribution.

I guess you will soon post an updated version
that makes use of the newer net_getrandom() stuff?

      reply	other threads:[~2004-08-18 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 19:31 [RFC] netem - enhancement Stephen Hemminger
2004-08-18 21:16 ` 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=20040818141600.1fd67e91.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 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.