public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
	Christoph Lameter <clameter@sgi.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] hotplug-memory: refactor online_pages to separate zone growth from page onlining
Date: Fri, 28 Mar 2008 22:48:21 -0700	[thread overview]
Message-ID: <47EDD825.20501@goop.org> (raw)
In-Reply-To: <20080329133820.e692245d.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> Hi,
>
> On Fri, 28 Mar 2008 17:00:05 -0700
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>   
>> -	if (onlined_pages)
>> +	if (onlined_pages) {
>> +		struct memory_notify arg;
>> +
>> +		arg.start_pfn = pfn;  /* ? */
>> +		arg.nr_pages = onlined_pages;
>> +		arg.status_change_nid = -1;  /* ? */
>> +
>>  		memory_notify(MEM_ONLINE, &arg);
>> +	}
>>     
> I think you should add "onlined" member instead of reusing nr_pages.
>   

I suppose.  What would I put into nr_pages?  And anyway, there are no 
users for this notification...

> But, in general, I have no objection to this way.
>   

The refactoring in general?

    J

  reply	other threads:[~2008-03-29  5:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  0:00 [PATCH RFC] hotplug-memory: refactor online_pages to separate zone growth from page onlining Jeremy Fitzhardinge
2008-03-29  0:47 ` Dave Hansen
2008-03-29  2:08   ` Jeremy Fitzhardinge
2008-03-29  6:01     ` Dave Hansen
2008-03-29 16:06     ` Dave Hansen
2008-03-29 23:53       ` Jeremy Fitzhardinge
2008-03-30  0:26         ` Anthony Liguori
2008-03-31 16:42         ` Dave Hansen
2008-03-31 18:06           ` Jeremy Fitzhardinge
2008-04-01  7:17             ` Yasunori Goto
2008-04-02 18:46             ` Dave Hansen
2008-04-02 18:52               ` Jeremy Fitzhardinge
2008-04-02 18:59                 ` Dave Hansen
2008-04-02 21:03                   ` Jeremy Fitzhardinge
2008-04-02 21:17                     ` Dave Hansen
2008-04-02 21:35                       ` Jeremy Fitzhardinge
2008-04-02 21:43                         ` Dave Hansen
2008-04-02 22:13                           ` Jeremy Fitzhardinge
2008-04-02 23:27                             ` Dave Hansen
2008-04-03  7:03                             ` KAMEZAWA Hiroyuki
2008-04-02 21:36                       ` Anthony Liguori
2008-03-29  4:38 ` KAMEZAWA Hiroyuki
2008-03-29  5:48   ` Jeremy Fitzhardinge [this message]
2008-03-29  6:26     ` KAMEZAWA Hiroyuki

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=47EDD825.20501@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=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