[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180522112230.GA5412@bombadil.infradead.org>
Date: Tue, 22 May 2018 04:22:30 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Huaisheng Ye <yehs2007@...il.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org, mhocko@...e.com,
vbabka@...e.cz, mgorman@...hsingularity.net,
kstewart@...uxfoundation.org, alexander.levin@...izon.com,
gregkh@...uxfoundation.org, colyli@...e.de, chengnt@...ovo.com,
hehy1@...ovo.com, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, xen-devel@...ts.xenproject.org,
linux-btrfs@...r.kernel.org, Huaisheng Ye <yehs1@...ovo.com>,
Minchan Kim <minchan@...nel.org>,
Nitin Gupta <ngupta@...are.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [RFC PATCH v2 10/12] mm/zsmalloc: update usage of address zone
modifiers
On Mon, May 21, 2018 at 11:20:31PM +0800, Huaisheng Ye wrote:
> @@ -343,7 +343,7 @@ static void destroy_cache(struct zs_pool *pool)
> static unsigned long cache_alloc_handle(struct zs_pool *pool, gfp_t gfp)
> {
> return (unsigned long)kmem_cache_alloc(pool->handle_cachep,
> - gfp & ~(__GFP_HIGHMEM|__GFP_MOVABLE));
> + gfp & ~__GFP_ZONE_MOVABLE);
> }
This should be & ~GFP_ZONEMASK
Actually, we should probably have a function to clear those bits rather
than have every driver manipulating the gfp mask like this. Maybe
#define gfp_normal(gfp) ((gfp) & ~GFP_ZONEMASK)
return (unsigned long)kmem_cache_alloc(pool->handle_cachep,
- gfp & ~(__GFP_HIGHMEM|__GFP_MOVABLE));
+ gfp_normal(gfp));
Powered by blists - more mailing lists