From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Robert Love <rml@tech9.net>
Cc: Andrew Morton <akpm@digeo.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: NUMA is bust with CONFIG_PREEMPT=y
Date: Wed, 02 Oct 2002 15:04:26 -0700 [thread overview]
Message-ID: <389320000.1033596266@flay> (raw)
In-Reply-To: <1033596139.27343.14.camel@phantasy>
>> 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.
What does it buy you on a large NUMA box over the low-latency patches?
> Besides, why screw yourself over from the day when preemption is a
> requirement? </semi-kidding> ;-)
A scary thought ....
M.
--
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:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 21:46 Andrew Morton
2002-10-02 21:49 ` Martin J. Bligh
2002-10-02 22:02 ` Robert Love
2002-10-02 22:04 ` Martin J. Bligh [this message]
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=389320000.1033596266@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=rml@tech9.net \
/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