From: Bill Davidsen <davidsen@oddball.prodigy.com>
To: Nick Piggin <piggin@cyberone.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler policy v15
Date: Fri, 12 Sep 2003 14:05:02 -0400 [thread overview]
Message-ID: <200309121405.02327.davidsen@oddball.prodigy.com> (raw)
In-Reply-To: <3F608807.9090705@cyberone.com.au>
On Thursday 11 September 2003 10:34 am, Nick Piggin wrote:
> Hi,
> http://www.kerneltrap.org/~npiggin/v15/
>
> This was going to get high res timers, but instead fixed a bug that might
> be causing a few people oopses. Also very small interactivity tweaks.
>
> I'm starting to work on SMP and NUMA ideas now, so if any interactivity
> things are bothering you, please tell me soon. I should be getting access
> to a 32-way NUMA soon, so I'm sort of holding off chaning too much until
> then.
>
> Enjoy.
The only odd behaviour I see with v15 (and also with v10) is that X
occasionally terminates when I unlock the screen. Haven't run pure test[45]
enough to say for sure that it doesn't happen there. Load was setiathome,
kernel make -j3, calculate PI to 20k places. System was responsive and
pleasant to use before I locked it, when I came back X died, system was still
stable.
RH 7.3 base, 2.6.0-test5+nick15, PII-350, 96MB, KDE
Next week I'll run pure test5 for a day and see what happens. I'll also get
some actual numbers on responsiveness (I think). After stability test I'll
run test5-mm1 (or latest) and look for the X oddity. So far Nick-v15 seems to
do a better job than test5-mm1, I don't have a sound card the system will use
at the moment.
--
Bill Davidsen
machine name and IP do not reflect reality, stealth in progress
next prev parent reply other threads:[~2003-09-12 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 14:34 Nick Piggin
2003-09-11 23:29 ` Cliff White
2003-09-12 4:43 ` Mike Fedyk
2003-09-12 18:05 ` Bill Davidsen [this message]
2003-09-12 18:39 ` Cliff White
2003-09-13 2:06 ` Nick Piggin
2003-09-13 11:17 ` Nick Piggin
2003-09-14 6:25 ` Cliff White
2003-09-22 5:40 ` Nick's scheduler policy v15a Nick Piggin
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=200309121405.02327.davidsen@oddball.prodigy.com \
--to=davidsen@oddball.prodigy.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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
all inboxes | Powered by JetHome®