From: bert hubert <ahu@ds9a.nl>
To: devik@cdi.cz
Cc: netdev@oss.sgi.com
Subject: 2.6.0-test4, 2.5.47, child qdiscs, parent not filled out?
Date: Wed, 3 Sep 2003 12:28:03 +0200 [thread overview]
Message-ID: <20030903102803.GA11876@outpost.ds9a.nl> (raw)
Devik (I hope we can be friends again :-)), others,
I'm currently working on the wondershaper 2.0 which is going to be much more
a massmarket product (still GPL, no worries), and I'm wondering why the
parent field of child qdiscs isn't filled out?
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?
Same holds for HTB and child qdiscs. Basically, I can't find a way to figure
out where qdiscs are actually attached. Or should I look for that in xstats?
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next reply other threads:[~2003-09-03 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 10:28 bert hubert [this message]
2003-09-03 21:01 ` 2.6.0-test4, 2.5.47, child qdiscs, parent not filled out? devik
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=20030903102803.GA11876@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=devik@cdi.cz \
--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).