[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170602071718.zk3ujm64xesoqyrr@sasha-lappy>
Date: Fri, 2 Jun 2017 07:17:22 +0000
From: "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>
To: Michal Hocko <mhocko@...nel.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Michal Hocko <mhocko@...e.com>,
John Hubbard <jhubbard@...dia.com>,
Andreas Dilger <adilger@...ger.ca>,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH 1/9] mm: introduce kv[mz]alloc helpers
On Mon, Mar 06, 2017 at 11:30:24AM +0100, Michal Hocko wrote:
> +void *kvmalloc_node(size_t size, gfp_t flags, int node)
> +{
> + gfp_t kmalloc_flags = flags;
> + void *ret;
> +
> + /*
> + * vmalloc uses GFP_KERNEL for some internal allocations (e.g page tables)
> + * so the given set of flags has to be compatible.
> + */
> + WARN_ON_ONCE((flags & GFP_KERNEL) != GFP_KERNEL);
Hm, there are quite a few locations in the kernel that do something like:
__vmalloc(len, GFP_NOFS, PAGE_KERNEL);
According to your patch, vmalloc can't really do GFP_NOFS, right?
--
Thanks,
Sasha
Powered by blists - more mailing lists