Hi All,
I am trying to use the for-next/pgtable branch with the top commit,
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
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
So it seems there is some issue with 16k only.
Need some inputs how to fix this
Regards,
Manish Jaggi
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
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
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
So it seems there is some issue with 16k only.
Need some inputs how to fix this
Regards,
Manish Jaggi
From: Suzuki.Poulose@arm.com (Suzuki K. Poulose) Date: 2016-03-01 11:23:09
On 01/03/16 10:48, 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
quoted
quoted
Observations:
a) During linux boot I see some oom messages
http://pastebin.com/8jSMFhqf
b) cat /proc/meminfo
MemTotal: 66613760 kB
MemFree: 307328 kB
MemAvailable: 22416 kB
Could you please provide the complete o/p of the following
with 16K ?
1) /proc/meminfo
2) /proc/buddyinfo
3) /proc/slabinfo
Thanks
Suzuki
From: Suzuki K. Poulose <Suzuki.Poulose@arm.com>
Sent: Tuesday, March 1, 2016 4:53 PM
To: Jaggi, Manish
Cc: linux-arm-kernel at lists.infradead.org; mark.rutland at arm.com
Subject: Re: for-next/pgtable branch: OOM error with 16K page size
On 01/03/16 10:48, Jaggi, Manish wrote:
quoted
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
quoted
quoted
quoted
Observations:
a) During linux boot I see some oom messages
http://pastebin.com/8jSMFhqf
b) cat /proc/meminfo
MemTotal: 66613760 kB
MemFree: 307328 kB
MemAvailable: 22416 kB
Could you please provide the complete o/p of the following
with 16K ?
1) /proc/meminfo
2) /proc/buddyinfo
3) /proc/slabinfo
That clearly tells you whats wrong. You have 2019x32M in hugepages.
Could you try releasing them and see if it solves the memory issue ?
$ echo 0 > /sys/kernel/mm/hugepages/hugepages-32768kB/nr_hugepages
btw, whats your root file system(to be more precise, the init) ?
Cheers
Suzuki
That clearly tells you whats wrong. You have 2019x32M in hugepages.
Could you try releasing them and see if it solves the memory issue ?
$ echo 0 > /sys/kernel/mm/hugepages/hugepages-32768kB/nr_hugepages
btw, whats your root file system(to be more precise, the init) ?
Also, could you get the number of HugePages_Total with 4K and 64K ?
May be your init (or whatever allocates the hugepages) requires some
hints about 16K and do something similar to what it does for 64K.
Thanks
Suzuki
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.