From: Stephen Anthony <stephena@cs.mun.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: What's the timeslice size for kernel 2.6.0-test2, IA32?
Date: Fri, 1 Aug 2003 14:04:46 -0230 [thread overview]
Message-ID: <200308011404.46886.stephena@cs.mun.ca> (raw)
>> I haven't been able to find this information anywhere. I know HZ was
>> increased to 1000, but was the timeslice decreased to 1 ms (from 10 ms)
>> as well?
>
> Depends on nice of the task. Nice 0 tasks get 102ms.
I don't think I asked the right question :) If I call usleep(x) or
nanosleep(x) with kernel 2.4.21, and x < 10, the sleep would still last
10 ms because of the timeslice. All sleeps would be a multiple of 10 ms.
If I call usleep(x) or nanosleep(x) in 2.6.0-test2, what 'multiple' can I
expect? Maybe I mean granularity instead of timeslice. Basically, I
want to know how 'soft' of a real-time system the new kernel is.
It would be great if sleeps were 1ms accurate instead of 10ms. It would
make synchronization code a lot easier.
Steve
next reply other threads:[~2003-08-01 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 16:34 Stephen Anthony [this message]
2003-08-01 18:34 ` Re: What's the timeslice size for kernel 2.6.0-test2, IA32? Mark Mielke
2003-08-01 19:29 ` Ben Greear
2003-08-02 9:25 ` george anzinger
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=200308011404.46886.stephena@cs.mun.ca \
--to=stephena@cs.mun.ca \
--cc=linux-kernel@vger.kernel.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