From: Ingo Molnar <mingo@elte.hu>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
tglx@linutronix.de, zippel@linux-m68k.org, rmk@arm.linux.org.uk,
schwidefsky@de.ibm.com, tony.luck@intel.com, davidm@hpl.hp.com,
clameter@sgi.com, george@mvista.com, ak@suse.de,
paulus@samba.org, benh@kernel.crashing.org, arnd@arndb.de
Subject: Re: [RFC][PATCHSET] Time: Generic Timeofday Subsystem (v B20)
Date: Sat, 4 Mar 2006 08:15:10 +0100 [thread overview]
Message-ID: <20060304071510.GA3893@elte.hu> (raw)
In-Reply-To: <1141447396.9727.139.camel@cog.beaverton.ibm.com>
* john stultz <johnstul@us.ibm.com> wrote:
> Summary:
> This patchset provides a generic timekeeping subsystem that is
> independent of the timer interrupt. This allows for robust and correct
> behavior in cases of late or lost ticks, avoids interpolation errors,
> reduces duplication in arch specific code, and allows or assists
> future changes such as high-res timers, dynamic ticks, or realtime
> preemption. Additionally, it provides finer nanosecond resolution
> values to the clock_gettime functions.
>
> Why do we need this?
i'd like to add the following to the list of reasons as well: the
current -hrt patch-queue (high resolution timers, which enables true
microsecond-level resolution for POSIX timers and nanosleep()), which is
working pretty well in the -rt tree and implements an important feature
for Linux, is based on the generic timekeeping subsystem as well.
Ingo
prev parent reply other threads:[~2006-03-04 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 4:43 john stultz
2006-03-04 7:15 ` Ingo Molnar [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=20060304071510.GA3893@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=clameter@sgi.com \
--cc=davidm@hpl.hp.com \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=zippel@linux-m68k.org \
/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