On Thu, Sep 03, 2015 at 05:43:29PM +0900, Yongtaek Lee wrote:
> > So, if we go and apply your logic to a 1GB system we should resize the
> > vmalloc area to 0 bytes in order to avoid RAM truncation without
> > CONFIG_HIGHMEM?
>
> As you already know, CONFIG_HIGHMEM option is necessary if RAM is
>
On Thu, Sep 03, 2015 at 10:34:32AM +0200, Lucas Stach wrote:
> Am Donnerstag, den 03.09.2015, 17:28 +0900 schrieb Yongtaek Lee:
> > As i know "vmalloc=size" is not mandatory so that i think default value of
> > vmalloc_min is wrong.
> >
> So, if we go and apply your logic to a 1GB system we shoul
> So, if we go and apply your logic to a 1GB system we should resize the
> vmalloc area to 0 bytes in order to avoid RAM truncation without
> CONFIG_HIGHMEM?
As you already know, CONFIG_HIGHMEM option is necessary if RAM is
more than 1GB. So no need to resize vmalloc area to 0.
> Sorry, but the
Am Donnerstag, den 03.09.2015, 17:28 +0900 schrieb Yongtaek Lee:
> > On Thu, Sep 03, 2015 at 11:24:47AM +0900, Yongtaek Lee wrote:
> > > default value of vmalloc_min was set 0xf000 for ARM by commit
> > > 0536bdf3. But actually vmalloc_min is 0xef80 not 0xf000.
> > >
> > > VMALLOC_END
> On Thu, Sep 03, 2015 at 11:24:47AM +0900, Yongtaek Lee wrote:
> > default value of vmalloc_min was set 0xf000 for ARM by commit
> > 0536bdf3. But actually vmalloc_min is 0xef80 not 0xf000.
> >
> > VMALLOC_END - (240 << 20) - VMALLOC_OFFSET)
> > 0xff00 - 0x0f00 - 0x0080 =
On Thu, Sep 03, 2015 at 11:24:47AM +0900, Yongtaek Lee wrote:
> default value of vmalloc_min was set 0xf000 for ARM by commit
> 0536bdf3. But actually vmalloc_min is 0xef80 not 0xf000.
>
> VMALLOC_END - (240 << 20) - VMALLOC_OFFSET)
> 0xff00 - 0x0f00 - 0x0080 = 0xef80
>
default value of vmalloc_min was set 0xf000 for ARM by commit
0536bdf3. But actually vmalloc_min is 0xef80 not 0xf000.
VMALLOC_END - (240 << 20) - VMALLOC_OFFSET)
0xff00 - 0x0f00 - 0x0080 = 0xef80
In case of 768MB ram without CONFIG_HIGHMEM=y, last 8MB could not be
all
7 matches
Mail list logo
