From: Andrew Morton <akpm@osdl.org>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu,
roe@sgi.com, steiner@sgi.com, clameter@sgi.com
Subject: Re: [PATCH] Call get_time() only when necessary in run_hrtimer_queue
Date: Fri, 24 Mar 2006 14:28:49 -0800 [thread overview]
Message-ID: <20060324142849.5cc27edb.akpm@osdl.org> (raw)
In-Reply-To: <20060324175136.GA10186@sgi.com>
Dimitri Sivanich <sivanich@sgi.com> wrote:
>
> It seems that run_hrtimer_queue() is calling get_time() much more often
> than it needs to.
>
> With this patch, it only calls get_time() if there's a pending timer.
>
> Following is from a profile done without the patch:
> kernel ticks: 30841 1.02 %
> 13572 44.01 44.01 time_interpolator_get_offset
> 155 0.50 96.91 hrtimer_run_queues
>
> And with the patch:
> kernel ticks: 18334 0.58 %
> 74 0.40 97.81 hrtimer_run_queues
> 43 0.23 98.63 time_interpolator_get_offset
>
>
This code has been extensively redone in -mm and I am planning on sending
all that to Linus within a week.
The hrtimer rework in -mm might fix this performance problem, although from
a quick peek, perhaps not.
So could you please verify that the problem still needs fixing in
2.6.16-mm1 and if so, raise a patch against that?
Thanks.
next prev parent reply other threads:[~2006-03-24 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 17:51 [PATCH] Call get_time() only when necessary in run_hrtimer_queue Dimitri Sivanich
2006-03-24 22:28 ` Andrew Morton [this message]
2006-03-25 7:01 ` Thomas Gleixner
2006-03-28 16:51 ` Dimitri Sivanich
2006-03-28 17:39 ` Eric Dumazet
2006-03-28 17:55 ` Dimitri Sivanich
2006-03-28 19:20 ` Thomas Gleixner
2006-03-28 20:14 ` [PATCH] Call get_softirq_time() only when necessary in run_hrtimer_queue() Dimitri Sivanich
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=20060324142849.5cc27edb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roe@sgi.com \
--cc=sivanich@sgi.com \
--cc=steiner@sgi.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