From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 0/6 v3] kvmalloc Date: Thu, 26 Jan 2017 04:14:37 -0800 Message-ID: <1485432877.12563.100.camel@perches.com> References: <588907AA.1020704@iogearbox.net> <20170126074354.GB8456@dhcp22.suse.cz> <5889C331.7020101@iogearbox.net> <20170126100802.GF6590@dhcp22.suse.cz> <20170126103216.GG6590@dhcp22.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Alexei Starovoitov , Andrew Morton , Vlastimil Babka , Mel Gorman , Johannes Weiner , linux-mm , LKML , "netdev@vger.kernel.org" , marcelo.leitner@gmail.com To: Michal Hocko , Daniel Borkmann Return-path: In-Reply-To: <20170126103216.GG6590@dhcp22.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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?