Re: [RFC PATCH 0/2] avoid external fragmentation related to migration fallback

2016-02-01 Thread Xishi Qiu
On 2016/2/1 21:53, Mel Gorman wrote: > On Fri, Jan 29, 2016 at 10:03:52PM +0100, Vlastimil Babka wrote: >>> Since the root cause is that fallbacks might frequently split order-2 >>> and order-3 pages of the other migration types. This patch tweaks >>> fallback mechanism to avoid splitting order-2

Re: [RFC PATCH 0/2] avoid external fragmentation related to migration fallback

2016-02-01 Thread Mel Gorman
On Fri, Jan 29, 2016 at 10:03:52PM +0100, Vlastimil Babka wrote: > > Since the root cause is that fallbacks might frequently split order-2 > > and order-3 pages of the other migration types. This patch tweaks > > fallback mechanism to avoid splitting order-2 and order-3 pages. while > > fallbacks h

Re: [RFC PATCH 0/2] avoid external fragmentation related to migration fallback

2016-01-30 Thread Xishi Qiu
On 2016/1/30 5:03, Vlastimil Babka wrote: > On 01/29/2016 08:23 PM, ChengYi He wrote: > > [...] > >> Below is the root cause of this external fragmentation which could be >> observed in devices which have only one memory zone, such as some arm64 >> android devices: >> >> 1) In arm64, the first 4

Re: [RFC PATCH 0/2] avoid external fragmentation related to migration fallback

2016-01-29 Thread Vlastimil Babka
On 01/29/2016 08:23 PM, ChengYi He wrote: [...] > Below is the root cause of this external fragmentation which could be > observed in devices which have only one memory zone, such as some arm64 > android devices: > > 1) In arm64, the first 4GB physical address space is of DMA zone. If the > size

[RFC PATCH 0/2] avoid external fragmentation related to migration fallback

2016-01-29 Thread ChengYi He
The patchset tries to avoid external fragmentation related to migration fallback. The symptom of this external fragmentation is that there are lots of allocation failures of order-2 and order-3 pages and many threads enter allocation slowpath to compact and direct reclaim pages. This will degrade s