From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Gilad Ben-Yossef <gilad@benyossef.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [patch 0/4] timers: Fix get_next_timer_interrupt() proper
Date: Fri, 25 May 2012 22:08:56 -0000 [thread overview]
Message-ID: <20120525214617.051888729@linutronix.de> (raw)
This series was inspired by the patch Gilad sent to fix a shortcoming
in get_next_timer_interrupt().
Instead of working around the problem I think it's better to avoid it
completely.
The fix is on top of a consolidation of the mindlessly copied code in
various timer API functions. Even with the added functionality that
makes the obj code footprint shrink
text data bss dec hex filename
18589 3682 8257 30528 7740 ../build/kernel/timer.o
17997 3682 8257 29936 74f0 ../build/kernel/timer.o
Thanks,
tglx
----
timer.c | 110 +++++++++++++++++++++++++++++++++++-----------------------------
1 file changed, 61 insertions(+), 49 deletions(-)
next reply other threads:[~2012-05-25 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 22:08 Thomas Gleixner [this message]
2012-05-25 22:08 ` [patch 1/4] timers: Create detach_if_pending() and use it Thomas Gleixner
2012-06-06 11:58 ` [tip:timers/core] " tip-bot for Thomas Gleixner
2012-05-25 22:08 ` [patch 2/4] timers: Consolidate base->next_timer update Thomas Gleixner
2012-05-29 6:34 ` Nikunj A Dadhania
2012-05-29 9:38 ` Thomas Gleixner
2012-05-29 10:35 ` Nikunj A Dadhania
2012-06-06 11:59 ` [tip:timers/core] " tip-bot for Thomas Gleixner
2012-05-25 22:08 ` [patch 3/4] timers: Add accounting of non deferrable timers Thomas Gleixner
2012-06-06 12:00 ` [tip:timers/core] " tip-bot for Thomas Gleixner
2012-05-25 22:08 ` [patch 4/4] timers: Improve get_next_timer_interrupt() Thomas Gleixner
2012-06-06 12:01 ` [tip:timers/core] " tip-bot for 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=20120525214617.051888729@linutronix.de \
--to=tglx@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=gilad@benyossef.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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