Re: [PATCH 17/20] dm: get rid of superfluous gfp flags

On Fri 29-04-16 14:54:52, Mike Snitzer wrote: > On Thu, Apr 28 2016 at 9:24am -0400, > Michal Hocko wrote: > > > From: Michal Hocko > > > > copy_params seems to be little bit confused about which allocation flags > > to use. It enforces GFP_NOIO even though

Re: [PATCH 17/20] dm: get rid of superfluous gfp flags

On Fri 29-04-16 14:54:52, Mike Snitzer wrote: > On Thu, Apr 28 2016 at 9:24am -0400, > Michal Hocko wrote: > > > From: Michal Hocko > > > > copy_params seems to be little bit confused about which allocation flags > > to use. It enforces GFP_NOIO even though it uses > >

Re: [PATCH 17/20] dm: get rid of superfluous gfp flags

On Thu, Apr 28 2016 at 9:24am -0400, Michal Hocko wrote: > From: Michal Hocko > > copy_params seems to be little bit confused about which allocation flags > to use. It enforces GFP_NOIO even though it uses > memalloc_noio_{save,restore} which enforces

Re: [PATCH 17/20] dm: get rid of superfluous gfp flags

On Thu, Apr 28 2016 at 9:24am -0400, Michal Hocko wrote: > From: Michal Hocko > > copy_params seems to be little bit confused about which allocation flags > to use. It enforces GFP_NOIO even though it uses > memalloc_noio_{save,restore} which enforces GFP_NOIO at the page > allocator level

[PATCH 17/20] dm: get rid of superfluous gfp flags

From: Michal Hocko copy_params seems to be little bit confused about which allocation flags to use. It enforces GFP_NOIO even though it uses memalloc_noio_{save,restore} which enforces GFP_NOIO at the page allocator level automatically (via memalloc_noio_flags). It also uses

[PATCH 17/20] dm: get rid of superfluous gfp flags

From: Michal Hocko copy_params seems to be little bit confused about which allocation flags to use. It enforces GFP_NOIO even though it uses memalloc_noio_{save,restore} which enforces GFP_NOIO at the page allocator level automatically (via memalloc_noio_flags). It also uses __GFP_REPEAT for the