From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
alan@lxorguk.ukuu.org.uk, anton@samba.org
Subject: Re: [patch] O(1) scheduler, 2.4.17-A1, 2.5.2-pre7-A1.
Date: Fri, 4 Jan 2002 22:41:08 -0500 [thread overview]
Message-ID: <20020104224108.430d7eac.johnpol@2ka.mipt.ru> (raw)
In-Reply-To: <Pine.LNX.4.33.0201041743050.8766-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0201041743050.8766-100000@localhost.localdomain>
On Fri, 4 Jan 2002 18:05:23 +0100 (CET)
Ingo Molnar <mingo@elte.hu> wrote:
>
> this is the next release of the O(1) scheduler:
>
> http://redhat.com/~mingo/O(1)-scheduler/sched-O1-2.5.2-A1.patch
> http://redhat.com/~mingo/O(1)-scheduler/sched-O1-2.4.17-A1.patch
>
> this release includes fixes and small improvements. (The 2.5.2-A1 patch
is
> against the 2.5.2-pre7 kernel.) I cannot reproduce any more failures
with
> this patch, but i couldnt test the vfat lockup problem. The X lockup
> problem never occured on any of my boxes, but it might be fixed by one
of
> the changes included in this patch nevertheless.
Nop. System hangs after couple of minutes in X mode... :(
vfat is compiled into the 2.4.17 vanilla-kernel.
Non smp i386 but with smp kernel.
Any other info?
>
> Ingo
---
WBR. //s0mbre
next prev parent reply other threads:[~2002-01-04 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 17:05 Ingo Molnar
2002-01-04 17:38 ` Andrey Nekrasov
2002-01-04 19:56 ` Ingo Molnar
2002-01-04 20:19 ` Adrian Bunk
2002-01-04 22:28 ` Ingo Molnar
2002-01-04 21:45 ` Heinz Diehl
2002-01-05 3:41 ` Evgeniy Polyakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 11:42 [announce] [patch] ultra-scalable O(1) SMP and UP scheduler Ingo Molnar
2002-01-04 22:44 ` [patch] O(1) scheduler, 2.4.17-A1, 2.5.2-pre7-A1 Dieter Nützel
2002-01-05 17:12 ` Adrian Bunk
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=20020104224108.430d7eac.johnpol@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
/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®