Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-04-18 Thread Johannes Weiner
On Thu, Apr 11, 2013 at 08:57:53PM +0100, Mel Gorman wrote: > Page reclaim at priority 0 will scan the entire LRU as priority 0 is > considered to be a near OOM condition. Kswapd can reach priority 0 quite > easily if it is encountering a large number of pages it cannot reclaim > such as pages

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-04-18 Thread Johannes Weiner
On Thu, Apr 11, 2013 at 08:57:53PM +0100, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under

[PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-04-11 Thread Mel Gorman
Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this happens, kswapd reclaims very aggressively

[PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-04-11 Thread Mel Gorman
Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this happens, kswapd reclaims very aggressively

[PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-04-09 Thread Mel Gorman
Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this happens, kswapd reclaims very aggressively

[PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-04-09 Thread Mel Gorman
Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this happens, kswapd reclaims very aggressively

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-21 Thread Michal Hocko
On Sun 17-03-13 13:04:11, Mel Gorman wrote: > Page reclaim at priority 0 will scan the entire LRU as priority 0 is > considered to be a near OOM condition. Kswapd can reach priority 0 quite > easily if it is encountering a large number of pages it cannot reclaim > such as pages under writeback.

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-21 Thread Rik van Riel
On 03/21/2013 06:12 AM, Mel Gorman wrote: On Wed, Mar 20, 2013 at 09:20:14PM -0400, Rik van Riel wrote: On 03/17/2013 09:04 AM, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-21 Thread Mel Gorman
On Wed, Mar 20, 2013 at 09:20:14PM -0400, Rik van Riel wrote: > On 03/17/2013 09:04 AM, Mel Gorman wrote: > >Page reclaim at priority 0 will scan the entire LRU as priority 0 is > >considered to be a near OOM condition. Kswapd can reach priority 0 quite > >easily if it is encountering a large

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-21 Thread Mel Gorman
On Wed, Mar 20, 2013 at 09:20:14PM -0400, Rik van Riel wrote: On 03/17/2013 09:04 AM, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-21 Thread Rik van Riel
On 03/21/2013 06:12 AM, Mel Gorman wrote: On Wed, Mar 20, 2013 at 09:20:14PM -0400, Rik van Riel wrote: On 03/17/2013 09:04 AM, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-21 Thread Michal Hocko
On Sun 17-03-13 13:04:11, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-20 Thread Rik van Riel
On 03/17/2013 09:04 AM, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this

Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-20 Thread Rik van Riel
On 03/17/2013 09:04 AM, Mel Gorman wrote: Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this

[PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-17 Thread Mel Gorman
Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this happens, kswapd reclaims very aggressively

[PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority

2013-03-17 Thread Mel Gorman
Page reclaim at priority 0 will scan the entire LRU as priority 0 is considered to be a near OOM condition. Kswapd can reach priority 0 quite easily if it is encountering a large number of pages it cannot reclaim such as pages under writeback. When this happens, kswapd reclaims very aggressively