Re: [RFC PATCH 3/3] mm: support active anti-fragmentation algorithm

2015-05-19 Thread Joonsoo Kim
On Tue, May 12, 2015 at 11:01:48AM +0200, Vlastimil Babka wrote: > On 04/28/2015 09:45 AM, Joonsoo Kim wrote: > >On Mon, Apr 27, 2015 at 09:29:23AM +0100, Mel Gorman wrote: > >>On Mon, Apr 27, 2015 at 04:23:41PM +0900, Joonsoo Kim wrote: > >>>We already have antifragmentation policy in page allocat

Re: [RFC PATCH 3/3] mm: support active anti-fragmentation algorithm

2015-05-12 Thread Vlastimil Babka
On 04/28/2015 09:45 AM, Joonsoo Kim wrote: On Mon, Apr 27, 2015 at 09:29:23AM +0100, Mel Gorman wrote: On Mon, Apr 27, 2015 at 04:23:41PM +0900, Joonsoo Kim wrote: We already have antifragmentation policy in page allocator. It works well when system memory is sufficient, but, it doesn't works w

Re: [RFC PATCH 3/3] mm: support active anti-fragmentation algorithm

2015-04-28 Thread Joonsoo Kim
On Mon, Apr 27, 2015 at 09:29:23AM +0100, Mel Gorman wrote: > On Mon, Apr 27, 2015 at 04:23:41PM +0900, Joonsoo Kim wrote: > > We already have antifragmentation policy in page allocator. It works well > > when system memory is sufficient, but, it doesn't works well when system > > memory isn't suff

Re: [RFC PATCH 3/3] mm: support active anti-fragmentation algorithm

2015-04-27 Thread Mel Gorman
On Mon, Apr 27, 2015 at 04:23:41PM +0900, Joonsoo Kim wrote: > We already have antifragmentation policy in page allocator. It works well > when system memory is sufficient, but, it doesn't works well when system > memory isn't sufficient because memory is already highly fragmented and > fallback/st

[RFC PATCH 3/3] mm: support active anti-fragmentation algorithm

2015-04-27 Thread Joonsoo Kim
We already have antifragmentation policy in page allocator. It works well when system memory is sufficient, but, it doesn't works well when system memory isn't sufficient because memory is already highly fragmented and fallback/steal mechanism cannot get whole pageblock. If there is severe unmovabl