From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, lartc@mailman.ds9a.nl
Subject: Re: [PATCH] (4/4) add loss option to network delay scheduler
Date: Fri, 18 Jun 2004 14:03:08 -0700 [thread overview]
Message-ID: <20040618140308.6405efed.davem@redhat.com> (raw)
In-Reply-To: <20040617155606.558d8eb3@dell_ss3.pdx.osdl.net>
On Thu, 17 Jun 2004 15:56:06 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> This enhances the network simulation scheduler to do simple random loss.
>
> The loss parameter is a simple 32 bit value such that 0 means no loss, and
> 0xffffffff is always drop. I have a new version of the tc command which takes
> care of conversion from percent to this value.
>
> Same patch for 2.4 and 2.6
Applied. But the 2.4.x side I had to apply by hand because in 2.4.x's
copy if pkt_sched.h there is no empty line before the final #endif
and thus patch rejected it.
prev parent reply other threads:[~2004-06-18 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 22:56 [PATCH] (4/4) add loss option to network delay scheduler Stephen Hemminger
2004-06-18 21:03 ` 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=20040618140308.6405efed.davem@redhat.com \
--to=davem@redhat.com \
--cc=lartc@mailman.ds9a.nl \
--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).