From: Micah Anderson <micah@riseup.net>
To: Ryan Reich <ryanr@uchicago.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: stable/vanilla+(O)1
Date: Sun, 15 Feb 2004 17:02:09 -0600 [thread overview]
Message-ID: <20040215230209.GP14140@riseup.net> (raw)
In-Reply-To: <402FF424.4050902@uchicago.edu>
I am aware that -ck patches have this, however it has a lot of other
things that I am not interested in entertaining. I want to isolate
variables, and getting preemptible, low latency and CK interactivity
in addition to O(1) makes it hard for me to gauge what is going on.
I prefer to change one thing at a time.
Micah
On Sun, 15 Feb 2004, Ryan Reich wrote:
> Micah Anderson wrote:
> >Is there a patch to the stable/vanilla 2.4 kernel tree which provides
> >the O(1) scheduler code from 2.6? The closest thing I can find is:
> >
> >http://people.redhat.com/mingo/O(1)-scheduler/sched-HT-2.4.22-ac1-A0
> >
> >which is for AC (and is also A0), is there a newer 2.4.23/24 patch
> >that works against stock? The above patch fails miserably against a
> >stock 2.4.22 kernel.
> >
> >There is ftp://ftp.kernel.org/pub/linux/kernel/people/rml/sched/ingo-O1/
> >the latest which is sched-O1-rml-2.4.20-rc3-1.patch, but that too
> >fails horribly on a stock 2.4.22.
> >
> >I've been crawling through list archives, but have yet to find
> >anything, so I am reduced to asking. :)
>
> The -ck patchset has this and numerous other fun things in it. It can be
> found at http://www.plumlocosoft.com/kernel/ .
>
> --
> Ryan Reich
> ryanr@uchicago.edu
next prev parent reply other threads:[~2004-02-15 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1pCCK-5S4-23@gated-at.bofh.it>
2004-02-15 22:35 ` stable/vanilla+(O)1 Ryan Reich
2004-02-15 23:02 ` Micah Anderson [this message]
2004-02-15 23:04 ` stable/vanilla+(O)1 Ryan Reich
2004-02-15 22:04 stable/vanilla+(O)1 Micah Anderson
2004-02-15 22:26 ` stable/vanilla+(O)1 Matt H.
2004-02-15 23:05 ` stable/vanilla+(O)1 Micah Anderson
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=20040215230209.GP14140@riseup.net \
--to=micah@riseup.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ryanr@uchicago.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.