From: "David S. Miller" <davem@redhat.com>
To: hadi@cyberus.ca
Cc: shemminger@osdl.org, netdev@oss.sgi.com, lartc@mailman.ds9a.nl
Subject: Re: [PATCH] packet delay scheduler
Date: Fri, 19 Mar 2004 14:21:12 -0800 [thread overview]
Message-ID: <20040319142112.0ad562fe.davem@redhat.com> (raw)
In-Reply-To: <1079707927.1032.42.camel@jzny.localdomain>
On 19 Mar 2004 09:52:07 -0500
jamal <hadi@cyberus.ca> wrote:
> The better alternative is to use the tc extension patches i have
> because then you could write little modules which do different things
> and cascade them.
I agree that this chaining idea of tc actions is the end-all-be-all
way to do this kind of stuff.
But for now we can put Stephen's delay scheduler in the tree, and I
don't see any real problem with that until your tc action changes
are ready for integration.
next prev parent reply other threads:[~2004-03-19 22:21 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
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 [this message]
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=20040319142112.0ad562fe.davem@redhat.com \
--to=davem@redhat.com \
--cc=hadi@cyberus.ca \
--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 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.