[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180521153055.GA18588@lst.de>
Date: Mon, 21 May 2018 17:30:55 +0200
From: Christoph Hellwig <hch@....de>
To: Huaisheng Ye <yehs2007@...il.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org, mhocko@...e.com,
willy@...radead.org, 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>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>
Subject: Re: [RFC PATCH v2 05/12] include/linux/dma-mapping: update usage
of address zone modifiers
On Mon, May 21, 2018 at 11:20:26PM +0800, Huaisheng Ye wrote:
> From: Huaisheng Ye <yehs1@...ovo.com>
>
> Use __GFP_ZONE_MASK to replace (__GFP_DMA | __GFP_HIGHMEM | __GFP_DMA32).
>
> ___GFP_DMA, ___GFP_HIGHMEM and ___GFP_DMA32 have been deleted from GFP
> bitmasks, the bottom three bits of GFP mask is reserved for storing
> encoded zone number.
> __GFP_DMA, __GFP_HIGHMEM and __GFP_DMA32 should not be operated with
>each others by OR.
You have to include me for the whole series, otherwise I have absolutely
no way to properly review your patch.
Powered by blists - more mailing lists