[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131023101012.GB2043@cmpxchg.org>
Date: Wed, 23 Oct 2013 11:10:12 +0100
From: Johannes Weiner <hannes@...xchg.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc: akpm@...ux-foundation.org, mgorman@...e.de, dave@...1.net,
tony.luck@...el.com, matthew.garrett@...ula.com, riel@...hat.com,
arjan@...ux.intel.com, srinivas.pandruvada@...ux.intel.com,
willy@...ux.intel.com, kamezawa.hiroyu@...fujitsu.com,
lenb@...nel.org, rjw@...k.pl, gargankita@...il.com,
paulmck@...ux.vnet.ibm.com, svaidy@...ux.vnet.ibm.com,
andi@...stfloor.org, isimatu.yasuaki@...fujitsu.com,
santosh.shilimkar@...com, kosaki.motohiro@...il.com,
linux-pm@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v4 16/40] mm: Introduce a "Region Allocator" to
manage entire memory regions
On Thu, Sep 26, 2013 at 04:47:34AM +0530, Srivatsa S. Bhat wrote:
> Today, the MM subsystem uses the buddy 'Page Allocator' to manage memory
> at a 'page' granularity. But this allocator has no notion of the physical
> topology of the underlying memory hardware, and hence it is hard to
> influence memory allocation decisions keeping the platform constraints
> in mind.
This is no longer true after patches 1-15 introduce regions and have
the allocator try to stay within the lowest possible region (patch
15). Which leaves the question what the following patches are for.
This patch only adds a data structure and I gave up finding where
among the helpers, statistics, and optimization patches an actual
implementation is.
Again, please try to make every single a patch a complete logical
change to the code base.
--
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