linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: keith <kmannth@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	matt dobson <colpatch@us.ibm.com>,
	John Stultz <johnstul@us.ibm.com>,
	Andy Whitcroft <andyw@uk.ibm.com>
Subject: Re: [RFC] [Patch] For booting a i386 numa system with no memory in a node
Date: Mon, 21 Feb 2005 12:39:21 -0800	[thread overview]
Message-ID: <1109018361.21720.3.camel@localhost> (raw)
In-Reply-To: <1109017040.9817.1638.camel@knk>

On Mon, 2005-02-21 at 12:17 -0800, keith wrote:
>   Attach is a patch that allows a i386 numa based system to boot without
> memory in a node.  It deals with the assumption that all nodes have
> memory.  

The diff is backwards :)

> -                       if (node_memory_chunk[j].start_pfn >= max_pfn)
> {
> -                               printk ("Ignoring chunk of memory
> reported in the SRAT (could be hot-add zone?)\n");
> -                               continue;
> -                       }

Could you print out the memory ranges, or sizes here?  Also, please add
a KERN_* level to it.  We might not want this unless the user has booted
with "debug".

> +               if (node_has_online_mem(nid)){
> +                       if (start > low) {

Instead of indenting another level, can you just put a continue in the
loop?  I think it makes it much easier to read.  

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

  reply	other threads:[~2005-02-21 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1106881119.2040.122.camel@cog.beaverton.ibm.com>
     [not found] ` <1106882150.2040.126.camel@cog.beaverton.ibm.com>
     [not found]   ` <1106937253.27125.6.camel@knk>
     [not found]     ` <1106938993.14330.65.camel@localhost>
     [not found]       ` <1106941547.27125.25.camel@knk>
     [not found]         ` <1106942832.17936.3.camel@arrakis>
     [not found]           ` <1108611260.9817.1227.camel@knk>
     [not found]             ` <1108654782.19395.9.camel@localhost>
     [not found]               ` <1108664637.9817.1259.camel@knk>
     [not found]                 ` <1108666091.19395.29.camel@localhost>
     [not found]                   ` <1108671423.9817.1266.camel@knk>
     [not found]                     ` <421510E9.3000901@us.ibm.com>
     [not found]                       ` <1108677113.32193.8.camel@localhost>
     [not found]                         ` <42152690.4030508@us.ibm.com>
     [not found]                           ` <9230000.1108666127@flay>
     [not found]                             ` <1108686742.6482.51.camel@localhost>
2005-02-21 20:17                               ` keith
2005-02-21 20:39                                 ` Dave Hansen [this message]
2005-02-21 22:03                                   ` keith
2005-02-21 22:24                                     ` Dave Hansen
2005-02-21 23:46                                       ` keith
2005-02-21 23:55                                         ` Dave Hansen
2005-02-22  0:09                                         ` Dave Hansen

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=1109018361.21720.3.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=andyw@uk.ibm.com \
    --cc=colpatch@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=kmannth@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    /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