From: Andi Kleen <ak@suse.de>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org,
"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>
Subject: Re: [discuss] [rfc] x86_64: Kconfig changes for NUMA
Date: Wed, 26 Oct 2005 23:39:36 +0200 [thread overview]
Message-ID: <200510262339.37326.ak@suse.de> (raw)
In-Reply-To: <20051026202017.GA3841@localhost.localdomain>
On Wednesday 26 October 2005 22:20, Ravikiran G Thirumalai wrote:
> How's this?
Looks good.
There is a small inaccuracy in the help text for K8 - dual core single
socket systems don't need NUMA - but I can fix that.
-Andi
next prev parent reply other threads:[~2005-10-26 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 7:09 [rfc] x86_64: Kconfig changes for NUMA Ravikiran G Thirumalai
2005-10-26 14:46 ` [discuss] " Andi Kleen
2005-10-26 20:20 ` Ravikiran G Thirumalai
2005-10-26 21:39 ` Andi Kleen [this message]
2005-10-27 1:40 ` Magnus Damm
2005-10-27 6:25 ` Magnus Damm
2005-10-27 7:50 ` Andi Kleen
2005-10-27 8:25 ` Magnus Damm
2005-10-27 8:31 ` Andi Kleen
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=200510262339.37326.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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