linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matt Tolentino <metolent@snoqualmie.dp.intel.com>
To: ak@muc.de, metolent@snoqualmie.dp.intel.com
Cc: akpm@osdl.org, apw@shadowen.org, haveblue@us.ibm.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch 2/4] add x86-64 Kconfig options for sparsemem
Date: Wed, 18 May 2005 09:43:48 -0700	[thread overview]
Message-ID: <200505181643.j4IGhm7S026977@snoqualmie.dp.intel.com> (raw)

>On Wed, May 18, 2005 at 08:24:41AM -0700, Matt Tolentino wrote:
>> 
>> Add the requisite arch specific Kconfig options to enable 
>> the use of the sparsemem implementation for NUMA kernels
>> on x86-64.
>
>How much did you test sparsemem on x86-64 NUMA ? 
>
>There are various cases that probably need to be checked,
>AMD with SRAT, AMD without SRAT, AMD with more than 4GB RAM, 
>Summit(?), NUMA EMULATION etc.
>
>If all that works I would have no problem with removing the
>old code.

As my disclaimer said, this has only been tested using
the NUMA EMULATION config option.  That's a big part of
the reason for sending this out  - to get further testing 
on real x86-64 NUMA systems, but without breaking the
current discontigmem code.  

I expect to be able to test this on at least one AMD system
at the local University systems lab, but haven't had a
chance to do so yet.

matt

--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

             reply	other threads:[~2005-05-18 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 16:43 Matt Tolentino [this message]
2005-05-18 16:53 ` Andi Kleen
2005-05-19 14:53   ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2005-05-18 15:24 Matt Tolentino
2005-05-18 16:25 ` 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=200505181643.j4IGhm7S026977@snoqualmie.dp.intel.com \
    --to=metolent@snoqualmie.dp.intel.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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