Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change

On Mon, Jul 18, 2016 at 03:50:25PM +0100, Mel Gorman wrote: > With node-lru, the locking is based on the pgdat. As Minchan pointed > out, there is an opportunity to reduce LRU lock release/acquire in > check_move_unevictable_pages by only changing lock on a pgdat change. > > Signed-off-by: Mel Gor

Re: [PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change

On Mon, Jul 18, 2016 at 03:50:25PM +0100, Mel Gorman wrote: > With node-lru, the locking is based on the pgdat. As Minchan pointed > out, there is an opportunity to reduce LRU lock release/acquire in > check_move_unevictable_pages by only changing lock on a pgdat change. > > Signed-off-by: Mel Gor

[PATCH 2/3] mm, vmscan: Release/reacquire lru_lock on pgdat change

With node-lru, the locking is based on the pgdat. As Minchan pointed out, there is an opportunity to reduce LRU lock release/acquire in check_move_unevictable_pages by only changing lock on a pgdat change. Signed-off-by: Mel Gorman --- mm/vmscan.c | 22 +++--- 1 file changed, 11