From: Dan Malek <dan@embeddededge.com>
To: Grant Likely <glikely@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
Tom Rini <trini@kernel.crashing.org>,
Kumar Gala <galak@freescale.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc32: add CONFIG_HZ
Date: Sat, 27 Aug 2005 20:48:04 -0400 [thread overview]
Message-ID: <d18c6049f1976912db9a7022a85c158a@embeddededge.com> (raw)
In-Reply-To: <20050827050422.GC7234@siegfried.thelikelysolution.ca>
On Aug 27, 2005, at 1:04 AM, Grant Likely wrote:
> What's the reason for clock jitter? Is it because most timeouts are
> set
> to multiples of 100, or some other reason?
Yes, the application interfaces are all defined as 100 Hz (10 mSec).
If the POSIX timer implementation is done properly, it should be
possible to determine the timer parameters to eliminate this, but
I doubt any applications do this. They all assume 10 mSec :-)
-- Dan
next prev parent reply other threads:[~2005-08-28 0:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 22:48 [PATCH] ppc32: add CONFIG_HZ Rune Torgersen
2005-08-26 22:54 ` Dan Malek
2005-08-26 22:55 ` Tom Rini
2005-08-26 23:07 ` Dan Malek
2005-08-26 23:13 ` Tom Rini
2005-08-27 5:04 ` Grant Likely
2005-08-28 0:48 ` Dan Malek [this message]
2005-08-28 2:19 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 19:15 Kumar Gala
2005-08-26 20:13 ` Dan Malek
2005-08-26 21:31 ` Tom Rini
2005-08-26 22:52 ` Dan Malek
2005-09-08 1:04 ` Marcelo Tosatti
2005-09-08 14:11 ` Kumar Gala
2005-09-08 15:53 ` Dan Malek
2005-08-29 15:31 ` Segher Boessenkool
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=d18c6049f1976912db9a7022a85c158a@embeddededge.com \
--to=dan@embeddededge.com \
--cc=akpm@osdl.org \
--cc=galak@freescale.com \
--cc=glikely@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).