netdev.vger.kernel.org archive mirror
 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: network delay simulation
Date: Tue, 16 Mar 2004 17:41:34 -0800	[thread overview]
Message-ID: <20040316174134.2f1da12a.davem@redhat.com> (raw)
In-Reply-To: <20040316151058.3cc2fa28@dell_ss3.pdx.osdl.net>

On Tue, 16 Mar 2004 15:10:58 -0800
Stephen Hemminger <shemminger@osdl.org> wrote:

> Probably "the cowboy way" would be to right a new net/scheduler to just
> do FIFO delay.
> 
> Any ideas/comments? Somebody have some code sitting in a drawer?

Probably a packet scheduler would be my first choice, you could then even
tag packets using classification and therefore delay differently for different
flows.

Another thing I've always wanted to do was add a "struct netdev *" argument
to dev_alloc_skb(), then we could do things like do SKB allocation failure
tests on drivers to stress them in low memory situations and weird patterns
of alloc failures.  Probably do this in a transitional way via a new routine
with a new name that drivers gradually move over to using.

The idea is that we provide an interface by which to upload some bit string
of alloc success/failure binary states, and at each alloc the state machine
just runs through the bits to decide whether to just quickly return NULL or
not.

  parent reply	other threads:[~2004-03-17  1:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 23:10 network delay simulation Stephen Hemminger
2004-03-16 23:00 ` Andi Kleen
2004-03-17  1:50   ` David S. Miller
2004-03-17  2:06     ` Andi Kleen
2004-03-18  3:17     ` Andrew Morton
2004-03-17  1:41 ` David S. Miller [this message]
2004-03-17 15:37   ` John Heffner
2004-03-17 16:09   ` jamal
2004-03-17 17:51     ` David S. Miller
2004-03-17 18:00       ` Stephen Hemminger
2004-03-17 18:25         ` David S. Miller
2004-03-18 20:04   ` [PATCH] packet delay scheduler Stephen Hemminger
2004-03-19  4:53     ` David S. Miller
2004-03-19 18:47       ` Stephen Hemminger
2004-03-23  2:50         ` David S. Miller
2004-03-19 14:52     ` jamal
2004-03-19 22:21       ` David S. Miller
2004-03-22 13:40         ` jamal
2004-03-17  2:40 ` network delay simulation Ben Greear

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=20040316174134.2f1da12a.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).