From: John Stultz <johnstul@us.ibm.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Jon Hunter <jon-hunter@ti.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Dynamic Tick and Deferrable Timer Support
Date: Mon, 09 Feb 2009 11:10:42 -0800 [thread overview]
Message-ID: <1234206642.10457.45.camel@jstultz-laptop> (raw)
In-Reply-To: <20090207092021.GD1411@ucw.cz>
On Sat, 2009-02-07 at 10:20 +0100, Pavel Machek wrote:
> On Thu 2009-01-29 09:36:00, john stultz wrote:
> > On Thu, Jan 29, 2009 at 8:29 AM, Jon Hunter <jon-hunter@ti.com> wrote:
> > > Pallipadi, Venkatesh wrote:
> > > I have spent several weeks trying to suppress kernel timers using the
> > > deferred timers and lengthen the sleep time. I am now able to get the device
> > > to sleep for minutes but I found that max_delta_ns is a limiting factor. I
> > > will be surprised if you can sleep for longer than ~2.15 seconds with the
> > > current implementation.
> >
> > As an aside, there are some further hardware limitations in the
> > timekeeping core that limit the amount of time the hardware can sleep.
> > For instance, the acpi_pm clocksource wraps every 2.5 seconds or so,
> > so we have to wake up periodically to sample it to avoid wrapping
> > issues.
> >
> > Just to be able to deal with all the different hardware out there, the
> > timekeeping core expects to wake up twice a second to do this
> > sampling. It may be possible to push this out if you are using other
>
> That's strange... I think I seen less than 2 wakeups per second on
> powertop...? (thinkpad x60, nothing exotic).
Yea, I don't think there is an interface that the timekeeping code
communicates that through. Probably a good idea to get that established
before folks try to push further then a second and end up with trouble
on hardware with short clocksources.
thanks
-john
next prev parent reply other threads:[~2009-02-09 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 20:03 Hunter, Jon
2009-01-15 6:16 ` Andrew Morton
2009-01-26 18:23 ` Hunter, Jon
2009-01-26 19:48 ` Pallipadi, Venkatesh
2009-01-26 21:41 ` Hunter, Jon
2009-01-27 18:36 ` Pallipadi, Venkatesh
2009-01-27 18:45 ` Pallipadi, Venkatesh
2009-01-29 16:29 ` Jon Hunter
2009-01-29 17:36 ` john stultz
2009-01-30 19:04 ` Jon Hunter
2009-01-30 20:29 ` john stultz
2009-02-07 9:20 ` Pavel Machek
2009-02-07 9:20 ` Pavel Machek
2009-02-09 19:10 ` John Stultz [this message]
2009-04-08 19:20 ` Hunter, Jon
2009-04-08 22:52 ` Andrew Morton
2009-04-09 15:02 ` Jon Hunter
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=1234206642.10457.45.camel@jstultz-laptop \
--to=johnstul@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=jon-hunter@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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
Powered by JetHome