linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Magnus Damm <magnus@valinux.co.jp>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	"A. P. Whitcroft [imap]" <andyw@uk.ibm.com>
Subject: Re: [PATCH] i386: single node SPARSEMEM fix
Date: Wed, 07 Sep 2005 10:28:36 -0700	[thread overview]
Message-ID: <1126114116.7329.16.camel@localhost> (raw)
In-Reply-To: <20050906035531.31603.46449.sendpatchset@cherry.local>

On Tue, 2005-09-06 at 12:56 +0900, Magnus Damm wrote:
> This patch for 2.6.13-git5 fixes single node sparsemem support. In the case
> when multiple nodes are used, setup_memory() in arch/i386/mm/discontig.c calls
> get_memcfg_numa() which calls memory_present(). The single node case with
> setup_memory() in arch/i386/kernel/setup.c does not call memory_present()
> without this patch, which breaks single node support.

First of all, this is really a feature addition, not a bug fix. :)

The reason we haven't included this so far is that we don't really have
any machines that need sparsemem on i386 that aren't NUMA.  So, we
disabled it for now, and probably need to decide first why we need it
before a patch like that goes in.

I actually have exactly the same patch that you sent out in my tree, but
it's just for testing.  Magnus, perhaps we can get some of my testing
patches in good enough shape to put them in -mm so that the non-NUMA
folks can do more sparsemem testing.  

-- Dave

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-09-07 17:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06  3:56 Magnus Damm
2005-09-07 17:28 ` Dave Hansen [this message]
2005-09-07 18:22   ` Martin J. Bligh
2005-09-07 18:27     ` Dave Hansen
2005-09-07 18:34       ` Martin J. Bligh
2005-09-07 23:49         ` Andrew Morton
2005-09-08  0:46           ` Dave Hansen
2005-09-08  1:54           ` Magnus Damm
2005-09-08  6:11           ` Martin J. Bligh
2005-09-08  6:36             ` Magnus Damm
2005-09-08  1:51       ` Magnus Damm
2005-09-08  1:45     ` Magnus Damm
2005-09-08  1:40   ` 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=1126114116.7329.16.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=andyw@uk.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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