From: john stultz <johnstul@us.ibm.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Steven Rostedt <rostedt@goodmis.org>,
george@mvista.com, mingo@elte.hu, akpm@osdl.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
ray-gmail@madrabbit.org, Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch 00/43] ktimer reworked
Date: Thu, 01 Dec 2005 16:58:06 -0800 [thread overview]
Message-ID: <1133485086.7605.9.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <91D50CB6-A9B0-4501-AAD2-7D80948E7367@mac.com>
On Thu, 2005-12-01 at 19:41 -0500, Kyle Moffett wrote:
> On Dec 01, 2005, at 19:29, Roman Zippel wrote:
> > Hi,
> >
> >> As for portablility, I believe John Stultz has some nice plugins
> >> coming to what timer source you want to use, so if there's a
> >> better way to get a time, these should make things easy to add.
> >
> > These plugins can do no magic, if the hardware timer is slow, the
> > whole thing gets slow.
>
> The point is that you could switch both the timer and timeout
> implementations to jiffies if you wanted to, at the expense of the
> accuracy that a lot of people care about.
While I'm not challenging the possibility of doing this, my timekeeping
work does not provide quite this level of flexibility you imply. Indeed
one could use jiffies as a clocksource, limiting all time users
(including ktimers) to jiffies resolution, but I would consider that to
be abusing the interface.
thanks
-john
next prev parent reply other threads:[~2005-12-02 0:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 23:56 Thomas Gleixner
2005-12-01 0:41 ` Andrew Morton
2005-12-01 2:19 ` Ingo Molnar
2005-12-01 3:32 ` Roman Zippel
2005-12-01 3:57 ` Kyle Moffett
2005-12-01 15:40 ` Roman Zippel
2005-12-01 16:22 ` Ray Lee
2005-12-01 16:51 ` Russell King
2005-12-01 17:44 ` Roman Zippel
2005-12-01 19:08 ` Steven Rostedt
2005-12-01 21:11 ` Roman Zippel
2005-12-01 22:03 ` Steven Rostedt
2005-12-02 0:29 ` Roman Zippel
2005-12-02 0:41 ` Kyle Moffett
2005-12-02 0:58 ` john stultz [this message]
2005-12-02 1:01 ` Roman Zippel
2005-12-02 1:09 ` Kyle Moffett
2005-12-02 1:24 ` Roman Zippel
2005-12-02 1:47 ` David Lang
2005-12-02 14:43 ` Roman Zippel
2005-12-02 15:41 ` Kyle Moffett
2005-12-07 9:35 ` James Bruce
2005-12-07 12:34 ` Roman Zippel
2005-12-07 14:15 ` Kyle Moffett
2005-12-07 15:03 ` Roman Zippel
2005-12-07 14:17 ` Steven Rostedt
2005-12-08 15:43 ` James Bruce
2005-12-02 2:51 ` Steven Rostedt
2005-12-04 1:28 ` Andrew James Wade
2005-12-05 19:40 ` Roman Zippel
2005-12-06 2:46 ` Andrew James Wade
2005-12-01 20:24 ` Andrew Morton
2005-12-01 21:19 ` Ingo Molnar
2005-12-01 21:51 ` Andrew Morton
2005-12-01 22:13 ` Kyle Moffett
2005-12-01 22:15 ` Christoph Hellwig
2005-12-02 0:02 ` Thomas Gleixner
2005-12-02 0:36 ` Kyle Moffett
2005-12-02 1:06 ` Andrew Morton
2005-12-02 14:42 ` John Stoffel
2005-12-02 2:21 ` Steven Rostedt
2005-12-02 0:46 ` Roman Zippel
2005-12-01 16:52 ` Roman Zippel
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=1133485086.7605.9.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mrmacman_g4@mac.com \
--cc=ray-gmail@madrabbit.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®