From: george anzinger <george@mvista.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Mark Mielke <mark@mark.mielke.cc>,
Stephen Anthony <stephena@cs.mun.ca>,
linux-kernel@vger.kernel.org
Subject: Re: What's the timeslice size for kernel 2.6.0-test2, IA32?
Date: Sat, 02 Aug 2003 02:25:52 -0700 [thread overview]
Message-ID: <3F2B83A0.7020205@mvista.com> (raw)
In-Reply-To: <3F2ABF7E.4060006@candelatech.com>
Ben Greear wrote:
>
> Mark Mielke wrote:
>
>> On Fri, Aug 01, 2003 at 02:04:46PM -0230, Stephen Anthony wrote:
>>
>>> It would be great if sleeps were 1ms accurate instead of 10ms. It
>>> would make synchronization code a lot easier.
>>
>>
>>
>> Doesn't this depend on what HZ you define for the kernel?
>>
>> If you want 1ms sleep, just set HZ to 1000HZ+, and give your process a
>> high priority?
As it currently stands in the 2.6 kernel for the i386, HZ is defined
as 1000. Since the PIT interrupt source can not hit this, the actual
timer interrupt period is 999848 nano seconds. The minimum sleep
interval nanosleep will take is 1 of these and since the time may
start between ticks it adds another to give a min sleep time of
999848+~1/2 of that depending on where the request falls in the time
period.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-08-02 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 16:34 Re: What's the timeslice size for kernel 2.6.0-test2, IA32? Stephen Anthony
2003-08-01 18:34 ` Mark Mielke
2003-08-01 19:29 ` Ben Greear
2003-08-02 9:25 ` george anzinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-01 15:51 Stephen Anthony
2003-08-01 16:13 ` Con Kolivas
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=3F2B83A0.7020205@mvista.com \
--to=george@mvista.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
--cc=stephena@cs.mun.ca \
/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