From: Robert Love <rml@tech9.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: NUMA is bust with CONFIG_PREEMPT=y
Date: 02 Oct 2002 18:02:19 -0400 [thread overview]
Message-ID: <1033596139.27343.14.camel@phantasy> (raw)
In-Reply-To: <384860000.1033595383@flay>
On Wed, 2002-10-02 at 17:49, Martin J. Bligh wrote:
> I'd favour the latter. It doesn't seem that useful on big machines like this,
> and adds significant complication ... anyone really want it on a NUMA box? If
> not, I'll make a patch to disable it for NUMA machines ...
I am not one of the 12 people in the world with a NUMA-Q, but I would
not like to see you disable kernel preemption.
I would really like to see it work on every architecture in every
configuration. Is it that hard to make the requisite changes to fix it
up?
If nothing else, I think you guys can _infinitely_ benefit from the
atomicity checking infrastructure that is now in place.
Besides, why screw yourself over from the day when preemption is a
requirement? </semi-kidding> ;-)
just my two bits,
Robert Love
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-02 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 21:46 NUMA is bust with CONFIG_PREEMPT=y Andrew Morton
2002-10-02 21:49 ` Martin J. Bligh
2002-10-02 22:02 ` Robert Love [this message]
2002-10-02 22:04 ` Martin J. Bligh
2002-10-02 22:15 ` Robert Love
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=1033596139.27343.14.camel@phantasy \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.