From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Patrick McHardy <kaber@trash.net>
Cc: davem@davemloft.net, devik@cdi.cz, netdev@vger.kernel.org
Subject: Re: [NET_SCHED 03/06]: Fix endless loops caused by inaccurate qlen counters (part 1)
Date: Mon, 20 Nov 2006 18:07:51 +0200 [thread overview]
Message-ID: <4561D2D7.20209@kolumbus.fi> (raw)
In-Reply-To: <4561C0DA.4080609@trash.net>
Patrick McHardy wrote:
> Mika Penttilä wrote:
>
>> Patrick McHardy wrote:
>>
>>
>>> Mika Penttilä wrote:
>>>
>>>
>>>
>>>> Are you sure you didn't mean to :
>>>>
>>>> + while ((parentid = sch->parent)) {
>>>> + sch = __qdisc_lookup(sch->dev, TC_H_MAJ(parentid));
>>>> + cops = sch->ops->cl_ops;
>>>> + if (!(sch->q.qlen -= n) && cops->qlen_notify) { <----
>>>>
>>>>
>>>
>>> We could do that, currently the qdiscs check themselves.
>>> The idea was mainly that they could be interested in
>>> other changes as well, for example for recalculating
>>> a deadline when the next packet in line changes.
>>>
>>>
>>>
>> But you call the notify before the decrement, which seems odd...
>>
>
>
> The notification notifies of changes in a _child_ qdisc of
> the qdisc that is notified, which already has its counter
> decremented. The qdisc's own counter is irrelevant for
> the qdisc itself, it doesn't make any difference whether
> it is decremented before or after the notification.
>
> -
>
Has already decremented where? As I read it you notify parent and
_after_ that decrement child's counter...
Also, shoudn't the return value of qdisc_lookup be check, I think it can
return NULL for default qdiscs.
--Mika
next prev parent reply other threads:[~2006-11-20 16:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 13:08 [NET_SCHED 00/06]: Fix endless dequeue loops Patrick McHardy
2006-11-20 13:08 ` [NET_SCHED 01/06]: sch_htb: perform qlen adjustment immediately in ->delete Patrick McHardy
2006-11-30 1:35 ` David Miller
2006-11-20 13:08 ` [NET_SCHED 02/06]: Set parent classid in default qdiscs Patrick McHardy
2006-11-30 1:35 ` David Miller
2006-11-20 13:08 ` [NET_SCHED 03/06]: Fix endless loops caused by inaccurate qlen counters (part 1) Patrick McHardy
2006-11-20 14:23 ` Mika Penttilä
2006-11-20 14:31 ` Patrick McHardy
2006-11-20 14:44 ` Mika Penttilä
2006-11-20 14:51 ` Patrick McHardy
2006-11-20 16:07 ` Mika Penttilä [this message]
2006-11-20 16:42 ` Patrick McHardy
2006-11-30 1:35 ` David Miller
2006-11-20 13:08 ` [NET_SCHED 04/06]: Fix endless loops (part 2): "simple" qdiscs Patrick McHardy
2006-11-24 12:33 ` Jarek Poplawski
2006-11-24 13:07 ` Patrick McHardy
2006-11-24 13:37 ` Jarek Poplawski
2006-11-27 6:46 ` Jarek Poplawski
2006-11-30 1:36 ` David Miller
2006-11-20 13:08 ` [NET_SCHED 05/06]: Fix endless loops (part 3): HFSC Patrick McHardy
2006-11-30 1:36 ` David Miller
2006-11-20 13:08 ` [NET_SCHED 06/06]: Fix endless loops (part 4): HTB Patrick McHardy
2006-11-20 13:39 ` Martin Devera
2006-11-23 8:39 ` Jarek Poplawski
2006-11-23 8:44 ` Patrick McHardy
2006-11-23 9:01 ` Jarek Poplawski
2006-11-23 9:07 ` Patrick McHardy
2006-11-23 9:32 ` Martin Devera
2006-11-23 9:48 ` Patrick McHardy
2006-11-23 10:59 ` Jarek Poplawski
2006-11-30 1:37 ` David 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=4561D2D7.20209@kolumbus.fi \
--to=mika.penttila@kolumbus.fi \
--cc=davem@davemloft.net \
--cc=devik@cdi.cz \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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).