[lkml]   [2016]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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 automatically (via memalloc_noio_flags). It also
> uses __GFP_REPEAT for the __vmalloc request which doesn't make much
> sense either because vmalloc doesn't rely on costly high order
> allocations. Let's just drop the __GFP_REPEAT and leave the further
> cleanup to later changes.
> Cc: Shaohua Li <>
> Cc: Mikulas Patocka <>
> Cc:
> Signed-off-by: Michal Hocko <>

I've taken this patch for 4.7 but editted the header, see:

 \ /
  Last update: 2016-04-29 21:21    [W:0.245 / U:6.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site