| To: | Tomas Szepe <szepe@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC/PATCH] IMQ port to 2.6 |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 25 Jan 2004 14:22:19 -0500 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040125164431.GA31548@louise.pinerecords.com> |
| Organization: | jamalopolis |
| References: | <20040125152419.GA3208@penguin.localdomain> <20040125164431.GA31548@louise.pinerecords.com> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
There has been no real good reason as to why IMQ is needed to begin with. It may be easy to use and has been highly publized (which is always a dangerous thing in Linux). Maybe lets take a step back and see how people use it. How and why do you use IMQ? Is this because you couldnt use the ingress qdisc? Note, the abstraction to begin with is in the wrong place - it sure is an easy and nice looking hack. So is the current ingress qdisc, but we are laying that to rest with TC extensions. cheers, jamal On Sun, 2004-01-25 at 11:44, Tomas Szepe wrote: > On Jan-25 2004, Sun, 16:24 +0100 > Marcel Sebek <sebek64@xxxxxxx> wrote: > > > I have ported IMQ driver from 2.4 to 2.6.2-rc1. > > Original version was from http://trash.net/~kaber/imq/. > > ... > > It would definitely be nice to see IMQ merged at last. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | FIX (was Re: Demonstration code on how to trigger tcp6_sock leak), David S. Miller |
|---|---|
| Next by Date: | 2.6 sis900 (and tlan?) multicast bug, Joseph Fannin |
| Previous by Thread: | Re: [RFC/PATCH] IMQ port to 2.6, Tomas Szepe |
| Next by Thread: | Re: [RFC/PATCH] IMQ port to 2.6, Vladimir B. Savkin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |