From: Robert Love <rml@tech9.net>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] preemptive kernel for 2.4.19-pre7-ac4
Date: 08 May 2002 09:39:56 -0700 [thread overview]
Message-ID: <1020875996.2084.121.camel@bigsur> (raw)
In-Reply-To: <20020508123221.GF22050@louise.pinerecords.com>
On Wed, 2002-05-08 at 05:32, Tomas Szepe wrote:
> > The preempt-kernel patch for 2.4.19-pre7-ac4 is now available at
> > http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.19-pre7-ac4-1.patch
>
> ... applies to -pre8-ac1 as well. Safe to use?
Yep. I sent Alan a few more scheduler updates - if he puts them in
pre8-ac2, that may break the diff but still nothing incompatible.
Always assume (with most patches, really) that if it applies, it is
fine.
An exception would be things like lock-break or low-latency that assume
intricate knowledge of the locking and calling semantics of functions.
If they apply, they should compile and boot, but a deadlock may lurk.
This is partly why these solutions are horrible to maintain or get right
and the preemptible kernel is a wiser long-term solution to latency and
such.
Robert Love
next prev parent reply other threads:[~2002-05-08 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 18:03 [PATCH] preemptive kernel for 2.4.19-pre7-ac4 Robert Love
2002-05-08 12:32 ` Tomas Szepe
2002-05-08 12:21 ` Zwane Mwaikambo
2002-05-08 16:39 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 10:59 Martin.Knoblauch
2002-05-08 11:01 ` William Lee Irwin III
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=1020875996.2084.121.camel@bigsur \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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