Re: [PATCH 06/10] mm: page_alloc: Distinguish between being unable to sleep, unwilling to unwilling and avoiding waking kswapd

2015-08-21 Thread Mel Gorman
On Fri, Aug 21, 2015 at 03:42:21PM +0200, Vlastimil Babka wrote: > On 08/12/2015 12:45 PM, Mel Gorman wrote: > >__GFP_WAIT has been used to identify atomic context in callers that hold > >spinlocks or are in interrupts. They are expected to be high priority and > >have access one of two watermarks

Re: [PATCH 06/10] mm: page_alloc: Distinguish between being unable to sleep, unwilling to unwilling and avoiding waking kswapd

2015-08-21 Thread Vlastimil Babka
On 08/12/2015 12:45 PM, Mel Gorman wrote: __GFP_WAIT has been used to identify atomic context in callers that hold spinlocks or are in interrupts. They are expected to be high priority and have access one of two watermarks lower than "min". __GFP_HIGH users get access to the first lower watermark

Re: [PATCH 06/10] mm: page_alloc: Distinguish between being unable to sleep, unwilling to unwilling and avoiding waking kswapd

2015-08-20 Thread Mel Gorman
On Wed, Aug 19, 2015 at 04:44:40PM +0200, Vlastimil Babka wrote: > > Unfortunately this is not as simple for all uses of GFP_TRANSHUGE. > Namely in __alloc_pages_slowpath() the checks could use __GFP_NO_KSWAPD as one > of the distinguishing flags, but to test for lack of __GFP_KSWAPD_RECLAIM, > t

Re: [PATCH 06/10] mm: page_alloc: Distinguish between being unable to sleep, unwilling to unwilling and avoiding waking kswapd

2015-08-19 Thread Vlastimil Babka
On 08/12/2015 12:45 PM, Mel Gorman wrote: > __GFP_WAIT has been used to identify atomic context in callers that hold > spinlocks or are in interrupts. They are expected to be high priority and > have access one of two watermarks lower than "min". __GFP_HIGH users get > access to the first lower wat

Re: [PATCH 06/10] mm: page_alloc: Distinguish between being unable to sleep, unwilling to unwilling and avoiding waking kswapd

2015-08-12 Thread Michal Hocko
On Wed 12-08-15 11:45:31, Mel Gorman wrote: > __GFP_WAIT has been used to identify atomic context in callers that hold > spinlocks or are in interrupts. They are expected to be high priority and > have access one of two watermarks lower than "min". __GFP_HIGH users get > access to the first lower w

[PATCH 06/10] mm: page_alloc: Distinguish between being unable to sleep, unwilling to unwilling and avoiding waking kswapd

2015-08-12 Thread Mel Gorman
__GFP_WAIT has been used to identify atomic context in callers that hold spinlocks or are in interrupts. They are expected to be high priority and have access one of two watermarks lower than "min". __GFP_HIGH users get access to the first lower watermark and can be called the "high priority reserv