All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Bob Picco <bob.picco@hp.com>
Cc: lhms <lhms-devel@lists.sourceforge.net>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH] no per-arch mem_map init
Date: Tue, 08 Feb 2005 17:17:30 -0800	[thread overview]
Message-ID: <1107911850.4716.52.camel@localhost> (raw)
In-Reply-To: <20050209010452.GA20515@localhost.localdomain>

On Tue, 2005-02-08 at 20:04 -0500, Bob Picco wrote:
> > -		mem_map = contig_page_data.node_mem_map = vmem_map;
> > +		NODE_DATA(0)->node_mem_map = vmem_map;
> This has to be changed to.
> 		mem_map = NODE_DATA(0)->node_mem_map = vmem_map;
> >  		free_area_init_node(0, &contig_page_data, zones_size,
> >  				    0, zholes_size);
> >  
> [snip]
> I actually submitted an identical change within my last patchset to lhms.

Good to know.  I hadn't actually noticed that bit in your patch.  It's
another good example why to split things up into as many small, logical
pieces as possible.  

> Not making this change requires changing use of mem_map throughout contig.c
> and one BUG assertion in init.c.  I haven't tested this patch but it was
> indirectly tested by me in FLATMEM configuration for lhms.

Hmm.  Do you really need the 'mem_map = ' part?  I *think*
free_area_init_node() calls alloc_node_mem_map(), which should do that
exact assignment for you.  

-- 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-09  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 19:37 [RFC][PATCH] no per-arch mem_map init Dave Hansen
2005-02-09  0:39 ` [Lhms-devel] " Yasunori Goto
2005-02-09  1:14   ` Dave Hansen
2005-02-09  1:04 ` Bob Picco
2005-02-09  1:17   ` Dave Hansen [this message]
2005-02-09  1:46     ` Bob Picco

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=1107911850.4716.52.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=bob.picco@hp.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.