From: conman@kolivas.net
To: linux-kernel@vger.kernel.org
Subject: Re: Combined performance patches for 2.4.19
Date: Fri, 23 Aug 2002 13:06:00 +1000 [thread overview]
Message-ID: <1030071960.3d65a698eb46a@kolivas.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0208222117100.18588-100000@coffee.psychology.mcmaster.ca>
Quoting Mark Hahn <hahn@physics.mcmaster.ca>:
> uh, great, but didn't the author of the preemptible patch
> say he didn't even want it in 2.4? I imagine Ingo must
> feel the same about O(1).
I'm not trying to get this patch included in mainstream 2.4
I did it for myself and the others who want to play with it.
> do you really think you need them? afaik, AKPM's tests
> show that the mainstream kernel is just fine wrt latency.
Nothing wrong with trying it out is there?
Quote: "One ancecdote's worth a thousand benchmarks"
Con Kolivas
next parent reply other threads:[~2002-08-23 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0208222117100.18588-100000@coffee.psychology.mcmaster.ca>
2002-08-23 3:06 ` conman [this message]
2002-08-22 7:33 Combined performance patches for 2.4.19 Con Kolivas
2002-08-22 21:39 ` J Sloan
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=1030071960.3d65a698eb46a@kolivas.net \
--to=conman@kolivas.net \
--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