| To: | hadi@xxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] packet delay scheduler |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Fri, 19 Mar 2004 14:21:12 -0800 |
| Cc: | shemminger@xxxxxxxx, netdev@xxxxxxxxxxx, lartc@xxxxxxxxxxxxxxx |
| In-reply-to: | <1079707927.1032.42.camel@xxxxxxxxxxxxxxxx> |
| References: | <20040316151058.3cc2fa28@xxxxxxxxxxxxxxxxxxxxx> <20040316174134.2f1da12a.davem@xxxxxxxxxx> <20040318120451.1c9ee286@xxxxxxxxxxxxxxxxxxxxx> <1079707927.1032.42.camel@xxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On 19 Mar 2004 09:52:07 -0500 jamal <hadi@xxxxxxxxxx> 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC, PATCH 3/5]: netfilter+ipsec - input hooks, Herbert Xu |
|---|---|
| Next by Date: | Deleting tun interface and NETLINK messages ordering, Pavlin Radoslavov |
| Previous by Thread: | Re: [PATCH] packet delay scheduler, jamal |
| Next by Thread: | Re: [PATCH] packet delay scheduler, jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |