From: Patrick McHardy <kaber@trash.net>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: Question: how to detect if a qdisc is root or not?
Date: Thu, 19 Jul 2007 01:39:58 +0200 [thread overview]
Message-ID: <469EA4CE.4000402@trash.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC3290340F87C@orsmsx414.amr.corp.intel.com>
Waskiewicz Jr, Peter P wrote:
>>You're right, thats a bug. TC_H_ROOT is the parent ID, which
>>is stored in sch->parent. IIRC its also passed to the
>>->init() function.
>
>
> Unfortunately it's not passed. It is passed into the ->change()
> function:
>
> static int prio_init(struct Qdisc *sch, struct rtattr *opt)
>
> static int prio_change(struct Qdisc *sch, u32 handle, u32 parent, struct
> rtattr **tca, unsigned long *arg)
>
> I did mess around with sch->parent a bit, with no success (it appears to
> be zero / unitialized). I'll keep investigating.
Its set after grafting the parent, which is after initialization.
I think what should work is to set it in qdisc_create instead,
sch_api.c around line 490:
+ sch->parent = handle;
if (handle == TC_H_INGRESS) {
sch->flags |= TCQ_F_INGRESS;
sch->stats_lock = &dev->ingress_lock;
...
and remove the initialization in qdisc_graft. That would additionally
have the benefit that ingress qdiscs also have it initialized properly.
next prev parent reply other threads:[~2007-07-18 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 23:16 Question: how to detect if a qdisc is root or not? Waskiewicz Jr, Peter P
2007-07-18 23:23 ` Patrick McHardy
2007-07-18 23:29 ` Waskiewicz Jr, Peter P
2007-07-18 23:39 ` Patrick McHardy [this message]
2007-07-18 23:42 ` Waskiewicz Jr, Peter P
2007-07-20 22:59 ` Waskiewicz Jr, Peter P
2007-07-21 4:01 ` Patrick McHardy
2007-07-21 5:33 ` David Miller
2007-07-21 18:31 ` Waskiewicz Jr, Peter P
2007-07-21 18:55 ` Waskiewicz Jr, Peter P
2007-07-22 16:24 ` Patrick McHardy
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=469EA4CE.4000402@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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).