From: Lee Revell <rlrevell@joe-job.com>
To: Dmytro Bablinyuk <dmytro.bablinyuk@rftechnology.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Preemptive patch for 2.4.25
Date: Mon, 15 Aug 2005 00:07:08 -0400 [thread overview]
Message-ID: <1124078828.4918.9.camel@mindpipe> (raw)
In-Reply-To: <ddp1vo$1fn$1@sea.gmane.org>
On Mon, 2005-08-15 at 13:25 +1000, Dmytro Bablinyuk wrote:
> I hope this is the right place to ask. My apologise if it's wrong.
> I have found 2.4.25-low-latency.patch.gz for the 2.4.25 kernel but I
> couldn't find preemptible patch for this version of kernel.
> I found preempt-kernel-rml-2.4.23-pre5-1.patch and
> preempt-kernel-rml-2.4.26-pre5-1.patch which are pretty close but not
> exactly for the same version.
Why would you run 2.4 if you need low latency? Any recent 2.6 kernel
will blow that out of the water.
Lee
next prev parent reply other threads:[~2005-08-15 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 3:25 Preemptive patch for 2.4.25 Dmytro Bablinyuk
2005-08-15 4:07 ` Lee Revell [this message]
2005-08-15 5:25 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2005-08-15 3:08 Dmytro Bablinyuk
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=1124078828.4918.9.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dmytro.bablinyuk@rftechnology.com.au \
--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