On Mon, May 30, 2016 at 7:15 PM, Mel Gorman wrote:
> On Thu, May 26, 2016 at 02:21:42PM -0700, Andrew Morton wrote:
>> On Thu, 5 May 2016 17:57:13 +1000 "Oliver O'Halloran"
>> wrote:
>>
>> > As a part of memory initialisation the architecture
On Thu, May 26, 2016 at 02:21:42PM -0700, Andrew Morton wrote:
> On Thu, 5 May 2016 17:57:13 +1000 "Oliver O'Halloran"
> wrote:
>
> > As a part of memory initialisation the architecture passes an array to
> > free_area_init_nodes() which specifies the max PFN of each memory
On Fri, May 27, 2016 at 7:21 AM, Andrew Morton
wrote:
> hm, this is all ten year old Mel code.
>
> What's the priority on this? What are the user-visible runtime
> effects, how many people are affected, etc?
Low priority. To get bitten by this you need to enable a
On Thu, 5 May 2016 17:57:13 +1000 "Oliver O'Halloran" wrote:
> As a part of memory initialisation the architecture passes an array to
> free_area_init_nodes() which specifies the max PFN of each memory zone.
> This array is not necessarily monotonic (due to unused zones) so
As a part of memory initialisation the architecture passes an array to
free_area_init_nodes() which specifies the max PFN of each memory zone.
This array is not necessarily monotonic (due to unused zones) so this
array is parsed to build monotonic lists of the min and max PFN for
each zone.