From: Nick Piggin <piggin@cyberone.com.au>
To: Eric <eric@cisu.net>
Cc: Brice Figureau <brice+lklm@daysofwonder.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: spurious temporary freeze, scheduler and preempt problem ?
Date: Thu, 19 Feb 2004 11:27:10 +1100 [thread overview]
Message-ID: <403402DE.4030400@cyberone.com.au> (raw)
In-Reply-To: <200402181212.06279.eric@cisu.net>
Eric wrote:
>On Wednesday 18 February 2004 9:26 am, Brice Figureau wrote:
>Someone correct me if I'm way off base, but have you tried
> scheduler=deadline
>To try the different kernel schedulers?
>Im not sure about the keyword, but do a quick google or search lkml and you'll
>see the correct keyword and the different schedulers you can try.
>
>
>
It's probably a CPU scheduler related problem, so this
wouldn't do much.
next prev parent reply other threads:[~2004-02-19 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 15:26 PROBLEM: spurious temporary freeze, scheduler and preempt problem ? Brice Figureau
2004-02-18 18:12 ` Eric
2004-02-19 0:27 ` Nick Piggin [this message]
2004-02-19 9:41 ` Brice Figureau
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=403402DE.4030400@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=brice+lklm@daysofwonder.com \
--cc=eric@cisu.net \
--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