[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170126122729.GL6590@dhcp22.suse.cz>
Date: Thu, 26 Jan 2017 13:27:29 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Joe Perches <joe@...ches.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>, Mel Gorman <mgorman@...e.de>,
Johannes Weiner <hannes@...xchg.org>,
linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
marcelo.leitner@...il.com
Subject: Re: [PATCH 0/6 v3] kvmalloc
On Thu 26-01-17 04:14:37, Joe Perches wrote:
> On Thu, 2017-01-26 at 11:32 +0100, Michal Hocko wrote:
> > So I have folded the following to the patch 1. It is in line with
> > kvmalloc and hopefully at least tell more than the current code.
> []
> > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> []
> > @@ -1741,6 +1741,13 @@ void *__vmalloc_node_range(unsigned long size, unsigned long align,
> > * Allocate enough pages to cover @size from the page level
> > * allocator with @gfp_mask flags. Map them into contiguous
> > * kernel virtual space, using a pagetable protection of @prot.
> > + *
> > + * Reclaim modifiers in @gfp_mask - __GFP_NORETRY, __GFP_REPEAT
> > + * and __GFP_NOFAIL are not supported
>
> Maybe add a BUILD_BUG or a WARN_ON_ONCE to catch new occurrences?
I would really like to not touch vmalloc in this series.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists