From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Mustafa Mesanovic <mustafa.mesanovic@de.ibm.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/Resend] timer stats: add quick check to avoid function calls
Date: Tue, 23 Jun 2009 17:08:03 +0200 [thread overview]
Message-ID: <20090623150803.GD13415@elte.hu> (raw)
In-Reply-To: <20090623161212.5af942c0@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
>
> When the kernel is configured with CONFIG_TIMER_STATS but timer stats
> are runtime disabled we still get calls to __timer_stats_timer_set_start_info
> which initializes some fields in the corresponding struct timer_list.
>
> So add some quick checks in the the timer stats setup functions to avoid
> function calls to __timer_stats_timer_set_start_info when timer stats are
> disabled.
>
> In an artificial workload that does nothing but playing ping pong with a
> single tcp packet via loopback this decreases cpu consumption by 1 - 1.5%.
>
> This is part of a modified function trace output on SLES11:
>
> perl-2497 [00] 28630647177732388 [+ 125]: sk_reset_timer <-tcp_v4_rcv
> perl-2497 [00] 28630647177732513 [+ 125]: mod_timer <-sk_reset_timer
> perl-2497 [00] 28630647177732638 [+ 125]: __timer_stats_timer_set_start_info <-mod_timer
> perl-2497 [00] 28630647177732763 [+ 125]: __mod_timer <-mod_timer
> perl-2497 [00] 28630647177732888 [+ 125]: __timer_stats_timer_set_start_info <-__mod_timer
> perl-2497 [00] 28630647177733013 [+ 93]: lock_timer_base <-__mod_timer
makes sense.
Only one very small detail:
>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> ---
>
> include/linux/hrtimer.h | 6 ++++++
> include/linux/timer.h | 4 ++++
> kernel/time/timer_stats.c | 16 ++++++++--------
> kernel/timer.c | 2 ++
> 4 files changed, 20 insertions(+), 8 deletions(-)
>
> Index: linux-2.6/include/linux/hrtimer.h
> ===================================================================
> --- linux-2.6.orig/include/linux/hrtimer.h
> +++ linux-2.6/include/linux/hrtimer.h
> @@ -438,12 +438,16 @@ extern void sysrq_timer_list_show(void);
> */
> #ifdef CONFIG_TIMER_STATS
>
> +extern int timer_stats_active;
> +
> extern void timer_stats_update_stats(void *timer, pid_t pid, void *startf,
> void *timerf, char *comm,
> unsigned int timer_flag);
>
> static inline void timer_stats_account_hrtimer(struct hrtimer *timer)
> {
> + if (likely(!timer->start_pid))
> + return;
> timer_stats_update_stats(timer, timer->start_pid, timer->start_site,
> timer->function, timer->start_comm, 0);
> }
> @@ -453,6 +457,8 @@ extern void __timer_stats_hrtimer_set_st
>
> static inline void timer_stats_hrtimer_set_start_info(struct hrtimer *timer)
> {
> + if (likely(!timer_stats_active))
> + return;
> __timer_stats_hrtimer_set_start_info(timer, __builtin_return_address(0));
> }
>
> Index: linux-2.6/include/linux/timer.h
> ===================================================================
> --- linux-2.6.orig/include/linux/timer.h
> +++ linux-2.6/include/linux/timer.h
> @@ -187,6 +187,8 @@ extern unsigned long get_next_timer_inte
> */
> #ifdef CONFIG_TIMER_STATS
>
> +extern int timer_stats_active;
Why is this declared twice, once in hrtimer.h and once in timer.h?
One should suffice, right?
Ingo
next prev parent reply other threads:[~2009-06-23 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 14:12 Heiko Carstens
2009-06-23 15:08 ` Ingo Molnar [this message]
2009-06-23 15:38 ` Heiko Carstens
2009-06-24 9:47 ` [tip:timers/urgent] timer stats: Optimize by adding " tip-bot for Heiko Carstens
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=20090623150803.GD13415@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mustafa.mesanovic@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--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
all inboxes | Powered by JetHome®