From: David Brownell <david-b@pacbell.net>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Tony Lindgren <tony@atomide.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"TK, Pratheesh Gangadhar" <pratheesh@ti.com>
Subject: Re: [PATCH] suppress needless timer reprogramming {tick-sched.c}
Date: Wed, 18 Jun 2008 09:28:41 -0700 [thread overview]
Message-ID: <200806180928.42084.david-b@pacbell.net> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162035B963D16@dlee02.ent.ti.com>
On Wednesday 18 June 2008, Woodruff, Richard wrote:
> >
> > As measured using ETM trace this drops my reprogramming penalty from
> > almost 60% CPU load down to 15% during high interrupt rate. If you like
> > I can send traces to show this.
More than doubling the available-for-real-use CPU time! Impressive.
I'd imagine that many systems using reprogrammable 32K timers for
scheduling could win from such a patch, although not necessarily
quite so visibly as on this ARM unless their CPU clocks were also
in the 500+ MHz range.
Seems like a "law of unintended consequences" here. Use a 32K
timer since it takes less power than a multi-MHz one, and so the
faster clocks can be gated off more comprehensively (in hardware)
to give more power savings. Then throw NO_HZ on top to get one
more increment of power savings ... whoops, it was assuming that
it was dirt cheap to reprogram timers, major badness!
- Dave
prev parent reply other threads:[~2008-06-18 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B6D69C3A9EBCA4BA5DA60D91302742904554EE1@dlee13.ent.ti.com>
[not found] ` <200805161055.17252.david-b@pacbell.net>
[not found] ` <13B9B4C6EF24D648824FF11BE8967162035B87F9B8@dlee02.ent.ti.com>
[not found] ` <200806150130.32901.david-b@pacbell.net>
2008-06-17 0:05 ` Woodruff, Richard
[not found] ` <13B9B4C6EF24D648824FF11BE8967162035B963D16@dlee02.ent.ti.com>
2008-06-18 16:28 ` David Brownell [this message]
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=200806180928.42084.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pratheesh@ti.com \
--cc=r-woodruff2@ti.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®