[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXJ85Nr6F=mn5DgfanwNA2s55=_LyQKbXLrxfTc6yZcAQ@mail.gmail.com>
Date: Wed, 14 Aug 2013 16:20:06 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Seth Jennings <sjenning@...ux.vnet.ibm.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"H. Peter Anvin" <hpa@...or.com>, Dave Hansen <dave@...1.net>,
Nathan Fontenot <nfont@...ux.vnet.ibm.com>,
Cody P Schafer <cody@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Lai Jiangshan <laijs@...fujitsu.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux MM <linux-mm@...ck.org>
Subject: Re: [RFC][PATCH] drivers: base: dynamic memory block creation
On Wed, Aug 14, 2013 at 2:52 PM, Seth Jennings
<sjenning@...ux.vnet.ibm.com> wrote:
> On Wed, Aug 14, 2013 at 02:37:26PM -0700, Yinghai Lu wrote:
> If I am understanding you correctly, you are suggesting we make the block size
> a boot time tunable. It can't be a runtime tunable since the memory blocks are
> currently created a boot time.
yes.
If could make it to be tunable at run-time, could be much better.
>
> On ppc64, we can't just just choose a memory block size since it must align
> with the underlying LMB (logical memory block) size, set in the hardware ahead
> of time.
assume for x86_64, it now support 46bits physical address. so if we
change to 2G, then
big system will only need create (1<<15) aka 32k entries in /sys at most.
Thanks
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/
Powered by blists - more mailing lists