* Changing PAGE_ALLOC_COSTLY_ORDER from 3 to 2
@ 2014-09-26 8:52 Pintu Kumar
0 siblings, 0 replies; only message in thread
From: Pintu Kumar @ 2014-09-26 8:52 UTC (permalink / raw)
To: mgorman, linaro-mm-sig, linux-arm-kernel, linux-mm, PINTU KUMAR,
pintu.k, linux-kernel
Hi,
I wanted to know about the impact of changing PAGE_ALLOC_COSTLY_ORDER value from 3 to 2.
This macro is defined in include/linux/mmzone.h
#define PAGE_ALLOC_COSTLY_ORDER 3
As I know this value should never be changed irrespective of the type of the system.
Is it good to change this value for RAM size: 512MB, 256MB or 128MB?
If anybody have changed this value and experience any kind of problem or benefits please let us know.
We noticed that for one of the Android product with 512MB RAM, the PAGE_ALLOC_COSTLY_ORDER was set to 2.
We could not figure out why this value was decreased from 3 to 2.
As per my analysis, I observed that kmalloc fails little early, if we change this value to 2.
This is also visible from the _slowpath_ in page_alloc.c
Apart from this we could not find any other impact.
If anybody is aware of any other impact, please let us know.
Thank you!
Regards,
Pintu Kumar
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-09-26 8:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-26 8:52 Changing PAGE_ALLOC_COSTLY_ORDER from 3 to 2 Pintu Kumar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).