From: devik <devik@cdi.cz>
To: bert hubert <ahu@ds9a.nl>
Cc: <netdev@oss.sgi.com>
Subject: Re: 2.6.0-test4, 2.5.47, child qdiscs, parent not filled out?
Date: Wed, 3 Sep 2003 23:01:45 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0309032258290.521-100000@devix> (raw)
In-Reply-To: <20030903102803.GA11876@outpost.ds9a.nl>
> Devik (I hope we can be friends again :-)), others,
yep I think so :-)
> If I create a cbq with several classes, and attach a qdisc to those classes,
> a later netlink dump (RTM_GETQDISCS) returns parent as 0:0 for that qdisc,
> is this right?
structure Qdisc has DEPRECATED field __parent pointing to parent
qdisc (aparently CBQ needs it).
There is no other "parent" info in the struct so it can't be returned
IMHO.
You will have to parse all clases from root to leaves.
Maybe we could add parent handle to qdisc but it is question to
Alexey probably - I'm not sure how complex would it be to keep
the field in sync ...
devik
next prev parent reply other threads:[~2003-09-03 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 10:28 2.6.0-test4, 2.5.47, child qdiscs, parent not filled out? bert hubert
2003-09-03 21:01 ` devik [this message]
2003-09-03 21:09 ` bert hubert
2003-09-05 12:00 ` jamal
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=Pine.LNX.4.33.0309032258290.521-100000@devix \
--to=devik@cdi.cz \
--cc=ahu@ds9a.nl \
--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).