From: Theodore Tso <tytso@mit.edu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Roland McGrath <roland@redhat.com>,
akpm@linux-foundation.org, mm-commits@vger.kernel.org,
npiggin@suse.de, drepper@redhat.com, oleg@tv-sign.ru,
sebastien.dugue@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [patch] change futex_wait() to hrtimers
Date: Mon, 12 Mar 2007 10:12:14 -0400 [thread overview]
Message-ID: <20070312141214.GG4372@thunk.org> (raw)
In-Reply-To: <20070312105826.GB11864@one.firstfloor.org>
On Mon, Mar 12, 2007 at 11:58:26AM +0100, Andi Kleen wrote:
> On Mon, Mar 12, 2007 at 12:00:20PM +0100, Thomas Gleixner wrote:
> > On Mon, 2007-03-12 at 12:27 +0100, Andi Kleen wrote:
> > > Ingo Molnar <mingo@elte.hu> writes:
> > > >
> > > > the only correct approach is the use of hrtimers, and a patch exists for
> > > > that - see below. This has been included in -rt for quite some time.
> > >
> > > But isn't that bad for power management? You'll likely get more
> > > idle wakeups, won't you?
> >
> > Why so ? It comes more precise, but only once.
>
> When it's clustered around the jiffies interval then wakeups from
> multiple processes will be somewhat batched. With a precise wakeup you'll
> get wakeups all over the jiffies period, won't you?
What we probably need in the long-term, and not just for high
precision wakeups, is we need a way for waiters (either in the kernel
or in userspace) to specify a desired precision in their timers. Is
it, "wake me up in a second, exactly", or "wake me up in a second,
plus or minus 10ms"? (or 50ms? or 100ms?).
This becomes especially important if we want the tickless code to
really shine as far as power management is concerned. Unfortunately,
the POSIX timer abstraction doesn't give this kind of flexibility
easily, so it's going to be a while before we see significant
userspace adoption of such a kernel feature, but I think it's
something that would be still worthwhile to add.
Regards,
- Ted
next prev parent reply other threads:[~2007-03-12 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703110814.l2B8EaI1007615@shell0.pdx.osdl.net>
[not found] ` <20070312011259.3834A1801C4@magilla.sf.frob.com>
2007-03-12 9:10 ` [patch] change futex_wait() to hrtimers Ingo Molnar
2007-03-12 9:16 ` Nick Piggin
2007-03-12 11:02 ` Ingo Molnar
2007-03-12 11:13 ` Nick Piggin
2007-03-12 11:19 ` Ingo Molnar
2007-03-12 11:29 ` Nick Piggin
2007-03-12 11:38 ` Ingo Molnar
2007-03-12 11:52 ` Nick Piggin
2007-03-12 12:21 ` Ingo Molnar
2007-03-12 12:36 ` Nick Piggin
2007-03-12 11:19 ` Thomas Gleixner
2007-03-12 11:27 ` Andi Kleen
2007-03-12 11:00 ` Thomas Gleixner
2007-03-12 10:58 ` Andi Kleen
2007-03-12 11:04 ` Ingo Molnar
2007-03-12 11:20 ` Andi Kleen
2007-03-12 11:28 ` Ingo Molnar
2007-03-12 14:12 ` Theodore Tso [this message]
2007-03-12 14:22 ` Andi Kleen
2007-03-12 14:31 ` Ingo Molnar
2007-03-12 14:32 ` Nick Piggin
2007-03-15 0:03 linux
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=20070312141214.GG4372@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=sebastien.dugue@bull.net \
--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