From: Grant Likely <glikely@gmail•com>
To: Dan Malek <dan@embeddededge•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: Fri, 26 Aug 2005 23:04:22 -0600 [thread overview]
Message-ID: <20050827050422.GC7234@siegfried.thelikelysolution.ca> (raw)
In-Reply-To: <da1e14409c0face6cee5b4d5fa750c00@embeddededge.com>
On Fri, Aug 26, 2005 at 07:07:01PM -0400, Dan Malek wrote:
>
> On Aug 26, 2005, at 6:55 PM, Tom Rini wrote:
>
> >Yes, it was. With 2.6.13 and on i386 (and other arches that actually
> >make use of the question) it can be any of 100, 250 or 1000.
>
> Well, 250 just seems wrong as I mentioned in a previous message.
> It will function, but an application is going to see lots of clock
> jitter
> unless you work in multiples of 100. My choices would be 100, 200,
> 500, or 1000.
What's the reason for clock jitter? Is it because most timeouts are set
to multiples of 100, or some other reason?
Thanks,
g.
next prev parent reply other threads:[~2005-08-27 5:15 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 [this message]
2005-08-28 0:48 ` Dan Malek
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=20050827050422.GC7234@siegfried.thelikelysolution.ca \
--to=glikely@gmail$(echo .)com \
--cc=akpm@osdl$(echo .)org \
--cc=dan@embeddededge$(echo .)com \
--cc=galak@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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