Thread (7 messages) read the whole thread 7 messages, 3 authors, 2016-03-01

for-next/pgtable branch: OOM error with 16K page size

From: mark.rutland@arm.com (Mark Rutland)
Date: 2016-03-01 11:32:51

Hi,

On Tue, Mar 01, 2016 at 10:48:02AM +0000, Jaggi, Manish wrote:
quoted
quoted
From: linux-arm-kernel <redacted> on behalf of Jaggi, Manish <redacted>
Sent: Monday, February 29, 2016 5:56 PM
To: linux-arm-kernel at lists.infradead.org
Subject: for-next/pgtable branch: OOM error with 16K page size

Hi All,

I am trying to use the for-next/pgtable branch with the top commit,
The same issue is observed with for-next/core branch
I take it that you do not see this issue on v4.5-rc4?
quoted
quoted
commit 068a17a5805dfbca4bbf03e664ca6b19709cc7a8
Author: Mark Rutland [off-list ref]
Date:   Mon Jan 25 11:45:12 2016 +0000

  arm64: mm: create new fine-grained mappings at boot

Setup: ARMv8, Cavium ThunderX, 48Cores 64G ram.
linux config: defconfig + 16k page size.

Observations:
a) During linux boot I see some oom messages
http://pastebin.com/8jSMFhqf
Could you try again with "efi=debug"? If possible, also
"memblock=debug", though the latter will hugely increase the dmesg
output.
quoted
quoted
b) cat /proc/meminfo

MemTotal:         66613760 kB
MemFree:          307328 kB
MemAvailable:      22416 kB

Available memory is very less compared to total.

c) With 64K pagesize
MemTotal:       66831552 kB
MemFree:         3541184 kB
MemAvailable:    3298752 kB
The former does look very odd.

Could you dump the full contents of /proc/meminfo for both of these
cases?

Thanks,
Mark.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help