public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>, Tejun Heo <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, numa: move bootnode definition into srat_64.c
Date: Thu, 03 Mar 2011 13:37:28 -0800	[thread overview]
Message-ID: <4D700A18.8070708@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103031251460.9993@chino.kir.corp.google.com>

On 03/03/2011 12:52 PM, David Rientjes wrote:
> On Wed, 2 Mar 2011, Yinghai Lu wrote:
> 
>> diff --git a/arch/x86/mm/srat_64.c b/arch/x86/mm/srat_64.c
>> index 8e9d339..7e5d0e9 100644
>> --- a/arch/x86/mm/srat_64.c
>> +++ b/arch/x86/mm/srat_64.c
>> @@ -26,6 +26,11 @@
>>  
>>  int acpi_numa __initdata;
>>  
>> +struct bootnode {
>> +	u64 start;
>> +	u64 end;
>> +};
>> +
>>  static struct bootnode nodes_add[MAX_NUMNODES];
>>  
>>  static __init int setup_node(int pxm)
> 
> Can we get rid of struct bootnode instead and simply reuse 
> struct numa_memblk?  The latter isn't actually tied to memblock and is a 
> generic representation of a node id and address range.

Yes, could be don later esp if the hotplug mem code would support 
more than one block add per node.

Yinghai

      reply	other threads:[~2011-03-03 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  1:20 [PATCH] x86, numa: move bootnode definition into srat_64.c Yinghai Lu
2011-03-03  6:32 ` Tejun Heo
2011-03-03 20:52 ` David Rientjes
2011-03-03 21:37   ` Yinghai Lu [this message]

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=4D700A18.8070708@kernel.org \
    --to=yinghai@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox