[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CA9E87A.3000807@austin.ibm.com>
Date: Mon, 04 Oct 2010 09:45:14 -0500
From: Nathan Fontenot <nfont@...tin.ibm.com>
To: balbir@...ux.vnet.ibm.com
CC: Dave Hansen <dave@...ux.vnet.ibm.com>, Robin Holt <holt@....com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linuxppc-dev@...ts.ozlabs.org, Greg KH <greg@...ah.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
steiner@....com
Subject: Re: [PATCH 7/9] v3 Define memory_block_size_bytes for powerpc/pseries
On 10/03/2010 01:27 PM, Balbir Singh wrote:
> * Dave Hansen <dave@...ux.vnet.ibm.com> [2010-10-03 11:11:01]:
>
>> On Sun, 2010-10-03 at 13:07 -0500, Robin Holt wrote:
>>> On Sun, Oct 03, 2010 at 11:25:00PM +0530, Balbir Singh wrote:
>>>> * Nathan Fontenot <nfont@...tin.ibm.com> [2010-10-01 13:35:54]:
>>>>
>>>>> Define a version of memory_block_size_bytes() for powerpc/pseries such that
>>>>> a memory block spans an entire lmb.
>>>>
>>>> I hope I am not missing anything obvious, but why not just call it
>>>> lmb_size, why do we need memblock_size?
>>>>
>>>> Is lmb_size == memblock_size after your changes true for all
>>>> platforms?
>>>
>>> What is an lmb? I don't recall anything like lmb being referred to in
>>> the rest of the kernel.
>>
>> Heh. It's the OpenFirmware name for a Logical Memory Block. Basically
>> what we use to determine the SECTION_SIZE on powerpc. Probably not the
>> best terminology to use elsewhere in the kernel.
>
> Agreed for the kernel, this patch was for powerpc/pseries, hence was
> checking in this context.
>
I don't really see a reason to name it lmb_size, it seems easier
to stick with the naming used by the rest of the kernel.
-Nathan
--
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/
Powered by blists - more mailing lists