From: Thomas Gleixner <tglx@linutronix.de>
To: Ashwin Chaugule <ashwinc@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [RFC] [PATCH 1/1] hrtimers: Cache next hrtimer
Date: Fri, 28 Aug 2009 00:51:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0908280045200.2888@localhost.localdomain> (raw)
In-Reply-To: <4A970103.7010804@codeaurora.org>
On Thu, 27 Aug 2009, Ashwin Chaugule wrote:
> Cached the hrtimer which causes the expire_next
> value to change. This is to avoid unnecessary re-programming
> of the clock events device.
You forgot to describe the application scenario which triggers this.
> @@ -843,16 +851,20 @@ static void __remove_hrtimer(struct hrtimer *timer,
> struct hrtimer_clock_base *base,
> unsigned long newstate, int reprogram)
> {
> - if (timer->state & HRTIMER_STATE_ENQUEUED) {
> + struct hrtimer *next_hrtimer = __get_cpu_var(hrtimer_bases).next_hrtimer;
> +
> + if (hrtimer_is_queued(timer)) {
> /*
> * Remove the timer from the rbtree and replace the
> * first entry pointer if necessary.
> */
> if (base->first == &timer->node) {
> base->first = rb_next(&timer->node);
> - /* Reprogram the clock event device. if enabled */
> - if (reprogram && hrtimer_hres_active())
> - hrtimer_force_reprogram(base->cpu_base);
> + if (next_hrtimer == timer) {
> + /* Reprogram the clock event device. if enabled */
> + if (reprogram && hrtimer_hres_active())
> + hrtimer_force_reprogram(base->cpu_base);
> + }
> }
> rb_erase(&timer->node, &base->active);
So if I'm not totally on the wrong track, that's the meat of the
patch.
Any reason why we can't solve that problem with checking
cpu_base->expires_next against the timer which is deleted ?
See the patently untested patch below.
Another question which arises is whether we should bother with the
reprogramming at all and just let the last programmed event happen
even when the corresponding timer has been removed.
Thanks,
tglx
---
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index 49da79a..91d099c 100644
--- a/kernel/hrtimer.c
+++ b/kernel/hrtimer.c
@@ -906,19 +906,30 @@ static void __remove_hrtimer(struct hrtimer *timer,
struct hrtimer_clock_base *base,
unsigned long newstate, int reprogram)
{
- if (timer->state & HRTIMER_STATE_ENQUEUED) {
- /*
- * Remove the timer from the rbtree and replace the
- * first entry pointer if necessary.
- */
- if (base->first == &timer->node) {
- base->first = rb_next(&timer->node);
- /* Reprogram the clock event device. if enabled */
- if (reprogram && hrtimer_hres_active())
- hrtimer_force_reprogram(base->cpu_base);
- }
- rb_erase(&timer->node, &base->active);
- }
+ ktime_t expires;
+
+ if (!(timer->state & HRTIMER_STATE_ENQUEUED))
+ goto out;
+
+ /*
+ * Remove the timer from the rbtree and replace the first
+ * entry pointer if necessary.
+ */
+ rb_erase(&timer->node, &base->active);
+
+ if (base->first != &timer->node)
+ goto out;
+
+ base->first = rb_next(&timer->node);
+ /* Reprogram the clock event device. if enabled */
+ if (!reprogram || !hrtimer_hres_active())
+ goto out;
+
+ expires = ktime_sub(hrtimer_get_expires(timer), base->offset);
+ if (base->cpu_base->expires_next.tv64 == expires.tv64)
+ hrtimer_force_reprogram(base->cpu_base);
+
+out:
timer->state = newstate;
}
next prev parent reply other threads:[~2009-08-27 22:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 21:51 [RFC] [PATCH 1/1] hrtimers: Cache next hrtimer Ashwin Chaugule
2009-08-27 21:56 ` Ashwin Chaugule
2009-08-27 22:51 ` Thomas Gleixner [this message]
2009-08-27 23:09 ` Ashwin Chaugule
2009-08-27 23:16 ` Thomas Gleixner
2009-08-28 5:56 ` Ashwin Chaugule
2009-08-28 11:17 ` Thomas Gleixner
2009-08-28 16:34 ` Ashwin Chaugule
2009-08-28 18:19 ` Thomas Gleixner
2009-08-28 20:27 ` Ashwin Chaugule
2009-08-30 6:06 ` Ashwin Chaugule
2009-08-30 8:36 ` Thomas Gleixner
2009-08-31 4:17 ` Ashwin Chaugule
2009-08-31 7:08 ` Thomas Gleixner
2009-09-01 3:13 ` Ashwin Chaugule
2009-09-03 17:48 ` Ashwin Chaugule
2009-09-15 9:09 ` [tip:timers/core] hrtimer: Eliminate needless reprogramming of clock events device tip-bot for Ashwin Chaugule
2009-09-15 15:19 ` tip-bot for Ashwin Chaugule
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=alpine.LFD.2.00.0908280045200.2888@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=ashwinc@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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