From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.13-rc7 Latency Question
Date: Sat, 27 Aug 2005 12:07:29 +0200 [thread overview]
Message-ID: <6bffcb0e050827030772a47f57@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508270524340.14692@p34>
Hi,
On 8/27/05, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
> These options are self-explanatory:
>
> x x ( ) No Forced Preemption (Server) x
> x x x ( ) Voluntary Kernel Preemption (Desktop) x
> x x x (X) Preemptible Kernel (Low-Latency Desktop) x x
>
>
>
> It says 100 HZ or 250 HZ is good for SMP systems; however, what if I am
> using a P4 machine with 1 CPU (HT), is 1000HZ still the way to go, as its
> not really 2 *REAL* cpus?
I use 1000HZ on my P4 machine, HT enabled, staircase scheduler.
See LKML topic "Schedulers benchmark" if you want more
information/benchmarks results.
Regards,
Michal Piotrowski
prev parent reply other threads:[~2005-08-27 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 9:26 Kernel 2.6.13-rc7 Latency Question Justin Piszcz
2005-08-27 10:07 ` Michal Piotrowski [this message]
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=6bffcb0e050827030772a47f57@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--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