From: Ingo Molnar <mingo@elte.hu>
To: Theodore Tso <tytso@mit.edu>, Andi Kleen <andi@firstfloor.org>,
Thomas Gleixner <tglx@linutronix.de>,
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
Cc: Arjan van de Ven <arjan@infradead.org>
Subject: Re: [patch] change futex_wait() to hrtimers
Date: Mon, 12 Mar 2007 15:31:18 +0100 [thread overview]
Message-ID: <20070312143118.GA27993@elte.hu> (raw)
In-Reply-To: <20070312141214.GG4372@thunk.org>
* Theodore Tso <tytso@mit.edu> wrote:
> 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?).
such a facility exists already, see round_jiffies() and
round_jiffies_relative(). There's some short blurb about it at:
http://kernelnewbies.org/LinuxChanges#head-513ceda14f5d8cf5b8a7c81d7e3821543141ecb0
> This becomes especially important if we want the tickless code to
> really shine as far as power management is concerned. [...]
yes. That's why we also implemented /proc/timer_stat, and this was
measured and a few higher-frequency fuzzy waiters were converted to use
round_jiffies(). Some other waiters were fixed in user-space. It's all
dependent on actual measurements and circumstances.
Ingo
next prev parent reply other threads:[~2007-03-12 14:32 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
2007-03-12 14:22 ` Andi Kleen
2007-03-12 14:31 ` Ingo Molnar [this message]
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=20070312143118.GA27993@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 \
--cc=tytso@mit.edu \
/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