public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Anton Blanchard <anton@samba.org>
Cc: Andy Whitcroft <apw@shadowen.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	Magnus Damm <magnus@valinux.co.jp>
Subject: Re: [PATCH] Allow flatmem to be disabled when only sparsemem is implemented
Date: Fri, 11 Nov 2005 19:41:31 +0000	[thread overview]
Message-ID: <4374F3EB.6040103@shadowen.org> (raw)
In-Reply-To: <4374DA3D.6050704@shadowen.org>

Andy Whitcroft wrote:
> Anton Blanchard wrote:
> 
>>On architectures that implement sparsemem but not discontigmem we want
>>to be able to hide the flatmem option in some cases. On ppc64 for
>>example, when we select NUMA we must not select flatmem.
> 
> First reaction is that this is very reasonable.  I can see why you need
> to do this as you don't have DISCONTIGMEM.  I will just go check the
> major architectures and make sure they arn't relying on being able to
> enable SPARSEMEM and getting FLATMEM too behaviour.  I don't think they
> can be as they all have DISCONTIGMEM and so should be insulated.

Ok.  I've reviewed the usage of the memory model selectors in the
architectures in 2.6.14-mm2.  It appears that only i386 is affected by
this change, the others that use the selector have explicit enablement
of FLATMEM.  This patch will interact badly with the current code to
enable SPARSEMEM on non-numa systems.  However, this code is under
review at this moment, and the proposed replacement (Message-ID:
<4370BC30.40100@shadowen.org>) is compatible with this change.

In short as long as they go in together this change looks good.

Magnus, any feedback on the replacement SPARSEMEM enabler on non-NUMA
i386 systems??

-apw

  reply	other threads:[~2005-11-11 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 16:03 [PATCH] Allow flatmem to be disabled when only sparsemem is implemented Anton Blanchard
2005-11-11 17:51 ` Andy Whitcroft
2005-11-11 19:41   ` Andy Whitcroft [this message]
2005-11-14  0:53     ` Magnus Damm

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=4374F3EB.6040103@shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus@valinux.co.jp \
    /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