From: Thomas Graf <tgraf@suug.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: jamal <hadi@cyberus.ca>, "David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com
Subject: Re: patch: annoying u32 double listing
Date: Sun, 6 Feb 2005 23:12:15 +0100 [thread overview]
Message-ID: <20050206221215.GW31837@postel.suug.ch> (raw)
In-Reply-To: <4206906A.2060501@trash.net>
* Patrick McHardy <4206906A.2060501@trash.net> 2005-02-06 22:47
> Thomas Graf wrote:
>
> >Another
> >quite anoying detail is the fact that cbq uses the same handle for
> >both the root qdisc and root class which makes it impossible to uniquely
> >assign filters attached to it, i.e. listing filters based on
> >parent == XX: && dev == %DEV will result in the filters being listed
> >for both the qdisc and the class.
> >
> CBQ and HFSC only support filters attached to classes for exactly this
> reason :) Shouldn't make any difference from a users perspective.
I'm aware of it and that's not the problem. The problem is that if the
user requests the filters attached to parent XX: he can't tell whether
the qdisc or class parent is meant without checking for hardcoded
qdisc kinds which makes it pretty much impossible to generate
qdisc/class/filter trees in a generic way. It's just something anoying
not a bug.
next prev parent reply other threads:[~2005-02-06 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 19:49 patch: annoying u32 double listing jamal
2005-02-06 20:44 ` 2.4.29 version: " jamal
2005-02-06 21:29 ` Thomas Graf
2005-02-06 21:42 ` jamal
2005-02-06 22:24 ` Thomas Graf
2005-02-06 21:47 ` Patrick McHardy
2005-02-06 22:12 ` Thomas Graf [this message]
2005-02-06 21:39 ` Patrick McHardy
2005-02-06 21:55 ` Patrick McHardy
2005-02-06 22:02 ` jamal
2005-02-06 23:17 ` Patrick McHardy
2005-02-07 6:36 ` David S. Miller
2005-02-07 13:49 ` jamal
2005-02-09 4:56 ` 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=20050206221215.GW31837@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).