From: "Matt H." <lkml@lpbproductions.com>
To: linux-kernel@vger.kernel.org
Subject: Re: stable/vanilla+(O)1
Date: Sun, 15 Feb 2004 15:26:31 -0700 [thread overview]
Message-ID: <200402151526.31560.lkml@lpbproductions.com> (raw)
In-Reply-To: <20040215220454.GL14140@riseup.net>
It's recommened you use 2.6.x if you want the O1 scheduler and newer things.
You can also use the -aa patchset for 2.4 , that contains the O1 Scheduler
and some vm tweaks.
Matt H.
On Sunday 15 February 2004 3:04 pm, 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. :)
>
> micah
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-02-15 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 22:04 stable/vanilla+(O)1 Micah Anderson
2004-02-15 22:26 ` Matt H. [this message]
2004-02-15 23:05 ` stable/vanilla+(O)1 Micah Anderson
[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 ` stable/vanilla+(O)1 Micah Anderson
2004-02-15 23:04 ` stable/vanilla+(O)1 Ryan Reich
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=200402151526.31560.lkml@lpbproductions.com \
--to=lkml@lpbproductions.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
all inboxes | Powered by JetHome®