[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1269922383.15854.68.camel@concordia>
Date: Tue, 30 Mar 2010 15:13:03 +1100
From: Michael Ellerman <michael@...erman.id.au>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH 07/31] lmb: Add reserve_lmb/free_lmb
On Mon, 2010-03-29 at 16:53 -0700, Yinghai Lu wrote:
> On 03/29/2010 04:34 PM, Benjamin Herrenschmidt wrote:
> > On Mon, 2010-03-29 at 15:37 -0700, Yinghai Lu wrote:
> >>> We just need a lmb.alloc_limit and a lmb_set_alloc_limit() which arch
> >>> code calls when it knows what the alloc limit is (and can call multiple
> >>> times during boot). Or maybe it should be called "default_alloc_limit",
> >>> but that's getting a bit long winded.
> >>
> >> ok, I will get_max_mapped() for now, an will change to new field...later
> >
> > No. Do it now. get_max_mapped() sucks as an identifier.
> >
>
> ok, can i reuse rmo_size, or introduce one new member in struct lmb.
>
> default_limit?
alloc_limit or default_alloc_limit
cheers
Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)
Powered by blists - more mailing lists