From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Phillips <phillips@arcor.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
Russell Lewis <spamhole-2001-07-16@deming-os.org>,
linux-kernel@vger.kernel.org
Subject: Re: Looking for links: Why Linux Doesn't Page Kernel Memory?
Date: 28 Jul 2002 21:07:36 +0100 [thread overview]
Message-ID: <1027886856.842.7.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <E17YcPU-00028D-00@starship>
On Sun, 2002-07-28 at 01:59, Daniel Phillips wrote:
> On Saturday 27 July 2002 18:24, David Woodhouse wrote:
> > ...Introduce it
> > slowly, adding it a little at a time like we did SMP, and like we _should_
> > have done preemption.
>
> I'll bite. How should we have done preemption?
By defaulting pre-emption off globally and working from the inside
adding pre-empt enable/disable pairs around blocks of code as they were
checked. Like the smp lock work but inside out.
That way egthe NE2000 driver might still work properly now, and be
working until its fixed.
next prev parent reply other threads:[~2002-07-28 18:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 17:59 Russell Lewis
2002-07-26 18:17 ` Andreas Dilger
2002-07-26 18:21 ` Robert Love
2002-07-26 19:10 ` Rik van Riel
2002-07-26 19:16 ` Robert Love
2002-07-26 19:18 ` Rik van Riel
2002-07-28 1:48 ` William Lee Irwin III
2002-07-28 1:56 ` Rik van Riel
2002-07-26 19:25 ` Richard B. Johnson
2002-07-26 19:33 ` Alan Cox
2002-07-26 19:43 ` Mike Castle
2002-07-27 16:24 ` David Woodhouse
2002-07-27 16:56 ` Rik van Riel
2002-07-28 0:59 ` Daniel Phillips
2002-07-28 20:07 ` Alan Cox [this message]
2002-07-28 0:40 ` Daniel Phillips
2002-07-28 0:57 ` 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=1027886856.842.7.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=spamhole-2001-07-16@deming-os.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®