From: Mike Fedyk <mfedyk@matchmail.com>
To: Robert Love <rml@tech9.net>
Cc: charles-heselton@cox.net,
Dieter N?tzel <Dieter.Nuetzel@hamburg.de>,
Dan Mann <mainlylinux@attbi.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
"J.A. Magallon" <jamagallon@able.es>
Subject: Re: Kernel 2.5.6 Interactive performance
Date: Sat, 9 Mar 2002 20:38:54 -0800 [thread overview]
Message-ID: <20020310043854.GA311@matchmail.com> (raw)
In-Reply-To: <NFBBKFIFGLNJKLMMGGFPKEPDCFAA.charles-heselton@cox.net> <1015734229.858.4.camel@phantasy>
In-Reply-To: <1015734229.858.4.camel@phantasy>
On Sat, Mar 09, 2002 at 11:23:48PM -0500, Robert Love wrote:
> On Sat, 2002-03-09 at 20:15, Charles Heselton wrote:
>
> > That would be great. I'm currently running 2.4.18. I'm always up for
> > things that would help improve performance, even if they are "experimental".
>
> A good base is Alan's tree, available at:
>
> http://www.kernel.org/pub/linux/kernel/people/alan/linux-2.4/2.4.19/patch-2.4.19-pre2-ac4.gz
>
> which is to be applied on top of 2.4.19-pre2. It contains the O(1)
> scheduler and rmap VM. If you are interested in preemption, the
> preempt-kernel patch is available at:
>
> http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/
>
> The 2.5 tree also has most of these toys, and is a better place for this
> development IMO. Personally, I'd stay away from these all-in-one silly
> patches that are floating around these days. Your safest bet is just
> stock 2.4.18 or whatever is latest, although the above addons are all at
> varying levels of "stable" and "safe".
>
Then what do you call -aa and -ac? ;)
These "all-in-one" patches do make it harder to debug specific patches, but
it does create a wider audience for many patches that wouldn't be used
otherwise.
next prev parent reply other threads:[~2002-03-10 4:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 19:55 Kernel 2.5.6 Interactive performance Dieter Nützel
2002-03-10 1:00 ` Charles Heselton
2002-03-10 1:11 ` Dieter Nützel
2002-03-10 1:15 ` Charles Heselton
2002-03-10 4:23 ` Robert Love
2002-03-10 4:38 ` Mike Fedyk [this message]
2002-03-10 6:05 ` Robert Love
2002-03-10 6:18 ` Charles Heselton
2002-03-10 4:55 ` J Sloan
2002-03-11 1:05 ` Andrea Arcangeli
[not found] <003301c1c7fd$a67d08f0$bb187143@amer.cisco.com>
2002-03-10 7:23 ` Charles Heselton
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 0:14 2.5.6-3 -- preempt_schedule unresolved in snd-pcm.o, snd-emu10k1-synth.o and snd-emu10k1.o Miles Lane
2002-03-09 18:55 ` Kernel 2.5.6 Interactive performance Dan Mann
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=20020310043854.GA311@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=charles-heselton@cox.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mainlylinux@attbi.com \
--cc=rml@tech9.net \
/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