linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1 of 6] hotplug-memory: refactor online_pages to separate zone growth from page onlining
Date: Thu, 03 Apr 2008 22:34:22 -0700	[thread overview]
Message-ID: <47F5BDDE.9060604@goop.org> (raw)
In-Reply-To: <20080404104358.C7F5.E1E9C6FF@jp.fujitsu.com>

Yasunori Goto wrote:
>> +/* Mark a set of pages as online */
>> +unsigned long mark_pages_onlined(unsigned long pfn, unsigned long nr_pages)
>> +{
>> +	struct zone *zone = page_zone(pfn_to_page(pfn));
>> +	unsigned long onlined_pages = 0;
>> +	int need_zonelists_rebuild = 0;
>>  
>>  	/*
>>  	 * If this zone is not populated, then it is not in zonelist.
>> @@ -240,10 +246,38 @@
>>  	vm_total_pages = nr_free_pagecache_pages();
>>  	writeback_set_ratelimit();
>>  
>> -	if (onlined_pages)
>> +	if (onlined_pages) {
>> +		struct memory_notify arg;
>> +
>> +		arg.start_pfn = pfn;  /* ? */
>> +		arg.nr_pages = onlined_pages;
>> +		arg.status_change_nid = -1;  /* ? */
>>     
>
> status_change_nid is to prepare data structures which are allocated on
> each NUMA node.
>   

OK.  I didn't really understand the intent this logic in the 
GOING_ONLINE notifier path:

	arg.status_change_nid = -1;

	nid = page_to_nid(pfn_to_page(pfn));
	if (node_present_pages(nid) == 0)
		arg.status_change_nid = nid;

and how that should relate to the ONLINE notifier.

> When memory less node gets new memory, and it changes status
> to normal memory, then status_change_nid must be set.
>
> SLUB uses it now.
>   

Only for GOING_ONLINE. 

    J

  reply	other threads:[~2008-04-04  5:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  0:05 [PATCH 0 of 6] [RFC] another attempt at making hotplug memory and xen play together Jeremy Fitzhardinge
2008-04-04  0:05 ` [PATCH 1 of 6] hotplug-memory: refactor online_pages to separate zone growth from page onlining Jeremy Fitzhardinge
2008-04-04  1:06   ` Dave Hansen
2008-04-04  1:20     ` Jeremy Fitzhardinge
2008-04-04  1:33       ` Dave Hansen
2008-04-04  1:09   ` Dave Hansen
2008-04-04  1:32     ` Jeremy Fitzhardinge
2008-04-04  1:41       ` Dave Hansen
2008-04-04  1:56   ` Yasunori Goto
2008-04-04  5:34     ` Jeremy Fitzhardinge [this message]
2008-04-04  0:05 ` [PATCH 2 of 6] xen: make phys_to_machine structure dynamic Jeremy Fitzhardinge
2008-04-04  0:05 ` [PATCH 3 of 6] xen-balloon: use memory hot-add to expand the domain's memory Jeremy Fitzhardinge
2008-04-04  0:05 ` [PATCH 4 of 6] hotplug-memory: use common online_page Jeremy Fitzhardinge
2008-04-04  0:47   ` Dave Hansen
2008-04-04  0:56     ` Jeremy Fitzhardinge
2008-04-04  1:00       ` Dave Hansen
2008-04-04  1:11         ` Jeremy Fitzhardinge
2008-04-04  1:22           ` Dave Hansen
2008-04-04  0:05 ` [PATCH 5 of 6] hotplug-memory: add section_ops Jeremy Fitzhardinge
2008-04-04  0:51   ` Dave Hansen
2008-04-04  1:12     ` Jeremy Fitzhardinge
2008-04-04  1:52       ` Dave Hansen
2008-04-04  5:32         ` Jeremy Fitzhardinge
2008-04-04 14:22           ` Dave Hansen
2008-04-04 18:21             ` Jeremy Fitzhardinge
2008-04-04 19:28               ` Christoph Lameter
2008-04-04 20:38                 ` Jeremy Fitzhardinge
2008-04-04  1:47     ` KAMEZAWA Hiroyuki
2008-04-04  5:35       ` Jeremy Fitzhardinge
2008-04-04  0:05 ` [PATCH 6 of 6] xen-balloon: define a section_ops Jeremy Fitzhardinge

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=47F5BDDE.9060604@goop.org \
    --to=jeremy@goop.org \
    --cc=clameter@sgi.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=y-goto@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).