From: Andi Kleen <ak@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: davem@redhat.com, netdev@oss.sgi.com
Subject: Re: network delay simulation
Date: Wed, 17 Mar 2004 00:00:48 +0100 [thread overview]
Message-ID: <20040317000048.10d9f52c.ak@suse.de> (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:
> Still bumming around for how to easily simulate long latencies.
> There is NISTnet but that is fugly old 2.2 code; and Dummynet, and hitbox
> which are FreeBSD based. The existing traffic shaper might do, but it seems
> to be limited to lower speed lines and needs some work (using atomic_set
> do own locking for instance).
>
> 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?
iirc there was a 2.4 port of NistNet. Porting it to 2.6 is probably
not that much work.
-Andi
next prev parent reply other threads:[~2004-03-16 23:00 UTC|newest]
Thread overview: 21+ 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 [this message]
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
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 ` [LARTC] [PATCH] packet delay scheduler Stephen Hemminger
2004-03-18 20:04 ` Stephen Hemminger
2004-03-19 4:53 ` David S. Miller
2004-03-19 18:47 ` [LARTC] " Stephen Hemminger
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=20040317000048.10d9f52c.ak@suse.de \
--to=ak@suse.de \
--cc=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.