From: Nick Piggin <nickpiggin@yahoo.com.au>
To: DaMouse <damouse@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler experiences
Date: Sun, 05 Sep 2004 22:56:09 +1000 [thread overview]
Message-ID: <413B0CE9.1090905@yahoo.com.au> (raw)
In-Reply-To: <1a56ea3904090505437e82b656@mail.gmail.com>
DaMouse wrote:
> On Sun, 05 Sep 2004 22:37:06 +1000, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>>DaMouse wrote:
>>
>>
>>>I personally like staircase, i also used to use nicksched but i prefer
>>>staircases simple design and structure. Nicksched was pretty fast but
>>>twiddling around all day with renicing X and now the HT issues are
>>>annoying and staircase has always worked perfectly for me without
>>>flipping fifty switches in the cockpit.
>>>
>>
>>The HT issue should be fixed (I hope).
>>
>>Why did you have to "twiddle around all day with renicing X"? I realise
>>you're overstating, but you really should be fine with just setting X
>>to -10 at startup and be done with it.
>>
>>
>
>
> http://forums.gentoo.org/viewtopic.php?t=217543 <-- see here, your
> mind makes it real... spooky :)
>
> Thats -mm2 but I can't find patches that fix the HT problems in that
> thread, mind pointing them out?
>
Hmm, OK I'll have another look at it. Thanks.
next prev parent reply other threads:[~2004-09-05 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 12:14 Scheduler experiences Kasper Sandberg
2004-09-05 12:25 ` DaMouse
2004-09-05 12:37 ` Nick Piggin
2004-09-05 12:43 ` DaMouse
2004-09-05 12:56 ` Nick Piggin [this message]
2004-09-05 12:49 ` Piotr Neuman
2004-09-05 14:25 ` Markus Törnqvist
2004-09-05 15:55 ` Scheduler experiences (with Reiser4 bug report) Markus Törnqvist
2004-09-05 16:07 ` Reiser4 bug Markus Törnqvist
2004-09-08 17:53 ` Scheduler experiences (with Reiser4 bug report) Bill Davidsen
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=413B0CE9.1090905@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=damouse@gmail.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