From: Matthew Wilcox <willy@infradead.org>
To: Huaisheng Ye <yehs1@lenovo.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, mhocko@suse.com,
vbabka@suse.cz, mgorman@techsingularity.net,
alexander.levin@verizon.com, colyli@suse.de, chengnt@lenovo.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] include/linux/gfp.h: getting rid of GFP_ZONE_TABLE/BAD
Date: Thu, 10 May 2018 09:30:23 -0700 [thread overview]
Message-ID: <20180510163023.GB30442@bombadil.infradead.org> (raw)
In-Reply-To: <1525968625-40825-1-git-send-email-yehs1@lenovo.com>
On Fri, May 11, 2018 at 12:10:25AM +0800, Huaisheng Ye wrote:
> -#define __GFP_DMA ((__force gfp_t)___GFP_DMA)
> -#define __GFP_HIGHMEM ((__force gfp_t)___GFP_HIGHMEM)
> -#define __GFP_DMA32 ((__force gfp_t)___GFP_DMA32)
> +#define __GFP_DMA ((__force gfp_t)OPT_ZONE_DMA ^ ZONE_NORMAL)
> +#define __GFP_HIGHMEM ((__force gfp_t)ZONE_MOVABLE ^ ZONE_NORMAL)
> +#define __GFP_DMA32 ((__force gfp_t)OPT_ZONE_DMA32 ^ ZONE_NORMAL)
No, you've made gfp_zone even more complex than it already is.
If you can't use OPT_ZONE_HIGHMEM here, then this is a waste of time.
> static inline enum zone_type gfp_zone(gfp_t flags)
> {
> enum zone_type z;
> - int bit = (__force int) (flags & GFP_ZONEMASK);
> + z = ((__force unsigned int)flags & ___GFP_ZONE_MASK) ^ ZONE_NORMAL;
> +
> + if (z > OPT_ZONE_HIGHMEM)
> + z = OPT_ZONE_HIGHMEM +
> + !!((__force unsigned int)flags & ___GFP_MOVABLE);
>
> - z = (GFP_ZONE_TABLE >> (bit * GFP_ZONES_SHIFT)) &
> - ((1 << GFP_ZONES_SHIFT) - 1);
> - VM_BUG_ON((GFP_ZONE_BAD >> bit) & 1);
> + VM_BUG_ON(z > ZONE_MOVABLE);
> return z;
> }
next prev parent reply other threads:[~2018-05-10 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:10 [PATCH v1] include/linux/gfp.h: getting rid of GFP_ZONE_TABLE/BAD Huaisheng Ye
2018-05-10 16:30 ` Matthew Wilcox [this message]
2018-05-11 3:24 ` [External] " Huaisheng HS1 Ye
2018-05-11 13:26 ` Matthew Wilcox
2018-05-12 11:35 ` Huaisheng HS1 Ye
2018-05-12 14:22 ` Matthew Wilcox
2018-05-16 12:12 ` Huaisheng HS1 Ye
2018-05-18 3:03 ` Huaisheng HS1 Ye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180510163023.GB30442@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=chengnt@lenovo.com \
--cc=colyli@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
--cc=yehs1@lenovo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).