From: matthew@sackman.co.uk (Matthew Sackman)
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] O(1) scheduler updates, -J2
Date: Sat, 19 Jan 2002 22:19:29 +0000 [thread overview]
Message-ID: <20020119221928.A2042@sackman.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0201181710520.10122-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0201181710520.10122-100000@localhost.localdomain>; from mingo@elte.hu on Fri, Jan 18, 2002 at 07:18:10PM +0100
On Fri, Jan 18, 2002 at 07:18:10PM +0100, Ingo Molnar wrote:
>
> the -J2 O(1) scheduler patch is available:
>
> http://redhat.com/~mingo/O(1)-scheduler/sched-O1-2.5.3-pre1-J2.patch
> http://redhat.com/~mingo/O(1)-scheduler/sched-O1-2.4.17-J2.patch
<snips>
Just a few comments on this. Compiled on 2.4.17 with gcc-2.95.4. O(1)-J2
only patch applied.
With the thread earlier regarding KDE and image thumbnails and xmms, yes
the machine is now useable whilst the images are being read and rendered,
and xmms doesn't falter, but about 2 seconds after kde finishes, xmms
falters twice (briefly - catches up very quickly).
Also, when X starts up, some of my startup settings seem to load too
quickly - I use uwm and a couple of xterms are started without the
terminal options being set (it seems) - instead of getting "user@host:~/"
on the left, I get each character on a seperate line. Also colours are
not fully set - mutt starts and then it seems the xterm bgcolour gets
applied.
Neither of these have ever happened without the O(1) patch. Please let
me know if I can be of any further assistance.
Matthew
next prev parent reply other threads:[~2002-01-19 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 18:18 [patch] O(1) scheduler updates, -J2 Ingo Molnar
2002-01-19 22:19 ` Matthew Sackman [this message]
2002-01-20 23:01 ` Matthew Sackman
2002-01-21 0:02 ` Martin Mačok
2002-01-21 18:46 ` Matthew Sackman
-- strict thread matches above, loose matches on Subject: below --
2002-01-20 0:19 James C. Owens
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=20020119221928.A2042@sackman.co.uk \
--to=matthew@sackman.co.uk \
--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