Re: [PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures

2015-11-30 Thread David Rientjes
On Thu, 26 Nov 2015, Michal Hocko wrote: > > > > > @@ -2642,6 +2644,13 @@ get_page_from_freelist(gfp_t gfp_mask, > > > > > unsigned int order, int alloc_flags, > > > > > if (zonelist_rescan) > > > > > goto zonelist_scan; > > > > > > > > > > + /* WARN only once unless min

Re: [PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures

2015-11-26 Thread Michal Hocko
On Wed 25-11-15 13:01:56, David Rientjes wrote: > On Wed, 25 Nov 2015, Michal Hocko wrote: > > > > > @@ -2642,6 +2644,13 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned > > > > int order, int alloc_flags, > > > > if (zonelist_rescan) > > > > goto zonelist_scan; > > > >

Re: [PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures

2015-11-25 Thread David Rientjes
On Wed, 25 Nov 2015, Michal Hocko wrote: > > > @@ -2642,6 +2644,13 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned > > > int order, int alloc_flags, > > > if (zonelist_rescan) > > > goto zonelist_scan; > > > > > > + /* WARN only once unless min_free_kbytes is updated */ > > > + i

Re: [PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures

2015-11-25 Thread Michal Hocko
On Wed 25-11-15 02:59:19, David Rientjes wrote: > On Wed, 25 Nov 2015, Michal Hocko wrote: [...] > > @@ -2642,6 +2644,13 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int > > order, int alloc_flags, > > if (zonelist_rescan) > > goto zonelist_scan; > > > > + /* WARN only on

Re: [PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures

2015-11-25 Thread David Rientjes
On Wed, 25 Nov 2015, Michal Hocko wrote: > From: Michal Hocko > > ALLOC_NO_WATERMARKS requests can dive into memory reserves without any > restriction. They are used only in the case of emergency to allow > forward memory reclaim progress assuming the caller should return the > memory in a short

[PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures

2015-11-25 Thread Michal Hocko
From: Michal Hocko ALLOC_NO_WATERMARKS requests can dive into memory reserves without any restriction. They are used only in the case of emergency to allow forward memory reclaim progress assuming the caller should return the memory in a short time (e.g. {__GFP,PF}_MEMALLOC requests or OOM victim