Re: [PATCH V2 2/2] mm/vmscan: not check compaction_ready on promoted zones

2014-02-14 Thread Mel Gorman
On Fri, Feb 14, 2014 at 02:42:34PM +0800, Weijie Yang wrote: > We abort direct reclaim if find the zone is ready for compaction. > Sometimes the zone is just a promoted highmem zone to force scan > pinning highmem, which is not the intended zone the caller want to > alloc page from. In this

Re: [PATCH V2 2/2] mm/vmscan: not check compaction_ready on promoted zones

2014-02-14 Thread Mel Gorman
On Fri, Feb 14, 2014 at 02:42:34PM +0800, Weijie Yang wrote: We abort direct reclaim if find the zone is ready for compaction. Sometimes the zone is just a promoted highmem zone to force scan pinning highmem, which is not the intended zone the caller want to alloc page from. In this situation,

[PATCH V2 2/2] mm/vmscan: not check compaction_ready on promoted zones

2014-02-13 Thread Weijie Yang
We abort direct reclaim if find the zone is ready for compaction. Sometimes the zone is just a promoted highmem zone to force scan pinning highmem, which is not the intended zone the caller want to alloc page from. In this situation, setting aborted_reclaim to indicate the caller turn back to

[PATCH V2 2/2] mm/vmscan: not check compaction_ready on promoted zones

2014-02-13 Thread Weijie Yang
We abort direct reclaim if find the zone is ready for compaction. Sometimes the zone is just a promoted highmem zone to force scan pinning highmem, which is not the intended zone the caller want to alloc page from. In this situation, setting aborted_reclaim to indicate the caller turn back to