All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir B. Savkin" <master@sectorb.msk.ru>
To: jamal <hadi@cyberus.ca>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC/PATCH] IMQ port to 2.6
Date: Sun, 25 Jan 2004 23:21:49 +0300	[thread overview]
Message-ID: <20040125202148.GA10599@usr.lcm.msu.ru> (raw)
In-Reply-To: <1075058539.1747.92.camel@jzny.localdomain>

On Sun, Jan 25, 2004 at 02:22:19PM -0500, jamal wrote:
> 
> 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?

Think multiple clients connected via PPP. I want to shape traffic,
so ingress is out of question. I want different clients in a same
htb class, so using qdisc on each ppp interface is out of
question. It seems to me that IMQ is the only way to achieve my goals.

> 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.
> 
> 
~
:wq
                                        With best regards, 
                                           Vladimir Savkin. 


  reply	other threads:[~2004-01-25 20:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 15:24 [RFC/PATCH] IMQ port to 2.6 Marcel Sebek
2004-01-25 16:44 ` Tomas Szepe
2004-01-25 19:22   ` jamal
2004-01-25 20:21     ` Vladimir B. Savkin [this message]
2004-01-25 23:45       ` jamal
2004-01-26  0:11         ` Vladimir B. Savkin
2004-01-26  3:09           ` jamal
2004-01-26  9:32             ` Vladimir B. Savkin
2004-01-26 13:38               ` jamal
2004-01-26 13:55                 ` Vladimir B. Savkin
2004-01-26 14:29                   ` jamal
2004-01-26 17:41                     ` Vladimir B. Savkin
2004-01-27  3:25                       ` jamal
2004-01-31 18:52                     ` Vladimir B. Savkin
2004-01-31 20:26                       ` jamal
2004-01-31 20:53                         ` Vladimir B. Savkin
2004-01-31 21:25                           ` jamal
2004-01-31 21:32                             ` Vladimir B. Savkin
2004-01-31 21:49                               ` jamal
2004-01-31 21:58                                 ` Vladimir B. Savkin
2004-01-31 22:26                                   ` jamal
2004-04-11 19:32                                     ` (Long) ANNOUNCE: IMQ replacement WAS(Re: " jamal
2004-01-26 15:24                   ` Tomas Szepe
2004-01-27  3:14                     ` jamal
2004-01-27 11:59                       ` Tomas Szepe
2004-01-31 17:02                         ` jamal
2004-01-25 19:25 ` David S. Miller
2004-01-25 20:23   ` Patrick McHardy
2004-01-25 21:55     ` David S. Miller

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=20040125202148.GA10599@usr.lcm.msu.ru \
    --to=master@sectorb.msk.ru \
    --cc=hadi@cyberus.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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.