Hi,
> > I suspect a big factor here is CONFIG_ARM64_64K_PAGES=y. Raspberry pi
> > 3, with standard fedora kernel (64k pages), minimal install (@core),
> > booted to the shell prompt. "free" reports ~122MB of memory as used.
> > Same with a self-compiled kernel (4k pages), I get ~44MB of used m
>> > I suspect a big factor here is CONFIG_ARM64_64K_PAGES=y. Raspberry pi
>> > 3, with standard fedora kernel (64k pages), minimal install (@core),
>> > booted to the shell prompt. "free" reports ~122MB of memory as used.
>> > Same with a self-compiled kernel (4k pages), I get ~44MB of used memo
On 02/16/2017 04:10 AM, Gerd Hoffmann wrote:
> What was the reason to go 64k pages in the first place?
Several reasons:
1). Some (server) implementations have higher performance under 64K.
2). VA sizes greater than 48-bit require a 64K translation granule. I
can mention that one publicly n
On 02/16/2017 10:36 AM, Christopher Covington wrote:
> Hi Peter, Paul, Laura,
>
> Feel free to drop the QDF2432 system register access erratum workaround
> patch at this point. Thanks for carrying it as long as you have. It has
> enabled additional testing and development that would have been muc
Hi,
> pressure on them to clean this up. RHEL (and Cent) will use 64K no
> matter what, but there could be a (short term) case for Fedora having
> a cycle or two with a smaller size - I would prefer to avoid that.
I think it would be more useful to offer a 4k kernel in addition to the
64k one,
On 02/16/2017 12:59 PM, Gerd Hoffmann wrote:
>> pressure on them to clean this up. RHEL (and Cent) will use 64K no
>> matter what, but there could be a (short term) case for Fedora having
>> a cycle or two with a smaller size - I would prefer to avoid that.
>
> I think it would be more useful to
W dniu 16.02.2017 o 18:59, Gerd Hoffmann pisze:
> I think it would be more useful to offer a 4k kernel in addition to
> the 64k one, similar to how Fedora ships kernel with and without
> lpae support on armv7.
Some applications still check PAGE_SIZE only during compilation instead
of on runtime.
