linux-kernel - Re: [PATCH] x86, numa: move bootnode definition into srat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 03 Mar 2011 13:37:28 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	David Rientjes <rientjes@...gle.com>
CC:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, Tejun Heo <tj@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86, numa: move bootnode definition into srat_64.c

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/