From: David Miller <davem@davemloft.net>
To: tglx@linutronix.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2]: pkt_sched: Convert CBQ to tasklet_hrtimer.
Date: Sun, 23 Aug 2009 18:54:56 -0700 (PDT) [thread overview]
Message-ID: <20090823.185456.25552109.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0908230919420.1769@localhost.localdomain>
From: Thomas Gleixner <tglx@linutronix.de>
Date: Sun, 23 Aug 2009 09:22:48 +0200 (CEST)
> B1;2005;0cOn Sat, 22 Aug 2009, David Miller wrote:
>> I'm not convinced either way, the code logic here has been like
>> this since at least 2.2.x, where it reads:
>>
>> if (!cl->delayed) {
>> unsigned long sched = jiffies;
>> ...
>> if (delay > 0) {
>> sched += PSCHED_US2JIFFIE(delay) + cl->penalty;
>> ...
>> if (del_timer(&q->delay_timer) &&
>> (long)(q->delay_timer.expires - sched) > 0)
>> q->delay_timer.expires = sched;
>> add_timer(&q->delay_timer);
>
> That does not make more sense than the hrtimer version :)
Sure it does, at least to me.
It says: When 'delay > 0', either the timer fires immediately
('jiffies') or at some point in the future ('jiffies + delay +
penalty' or existing expiration, whichever is sooner).
The intention of the code seems very clear.
>> So please review my patch in the context of a straight conversion to
>> tasklet_hrtimer, and let's deal with the timer offset logic here
>> seperately (and in -next, not 2.6.31-rcX)
>
> The straight conversion looks fine. Add my Acked-by.
Thanks.
next prev parent reply other threads:[~2009-08-24 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 0:03 [PATCH 2/2]: pkt_sched: Convert CBQ to tasklet_hrtimer David Miller
2009-08-22 9:17 ` Thomas Gleixner
2009-08-23 1:08 ` David Miller
2009-08-23 7:22 ` Thomas Gleixner
2009-08-24 1:54 ` David Miller [this message]
2009-08-28 15:54 ` Eric Dumazet
2009-08-28 19:30 ` David Miller
2009-08-28 19:51 ` Thomas Gleixner
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=20090823.185456.25552109.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).