From: Matthew Wilcox <willy@infradead.org>
To: Huaisheng HS1 Ye <yehs1@lenovo.com>
Cc: Michal Hocko <mhocko@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"pasha.tatashin@oracle.com" <pasha.tatashin@oracle.com>,
"alexander.levin@verizon.com" <alexander.levin@verizon.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"penguin-kernel@I-love.SAKURA.ne.jp"
<penguin-kernel@I-love.SAKURA.ne.jp>,
"colyli@suse.de" <colyli@suse.de>,
NingTing Cheng <chengnt@lenovo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH 2/3] include/linux/gfp.h: use unsigned int in gfp_zone
Date: Sun, 6 May 2018 11:55:32 -0700 [thread overview]
Message-ID: <20180506185532.GA13604@bombadil.infradead.org> (raw)
In-Reply-To: <HK2PR03MB168447008C658172FFDA402992840@HK2PR03MB1684.apcprd03.prod.outlook.com>
On Sun, May 06, 2018 at 04:17:06PM +0000, Huaisheng HS1 Ye wrote:
> Upload my current patch and testing platform info for reference. This patch has been tested
> on a two sockets platform.
Thank you!
> It works, but some drivers or subsystem shall be modified to fit
> these new type __GFP flags.
> They use these flags directly to realize bit manipulations like this
> below.
>
> eg.
> swiotlb-xen.c (drivers\xen): flags &= ~(__GFP_DMA | __GFP_HIGHMEM);
> extent_io.c (fs\btrfs): mask &= ~(__GFP_DMA32|__GFP_HIGHMEM);
>
> Because of these flags have been encoded within this patch, the
> above operations can cause problem.
I don't think this actually causes problems. At least, no additional
problems. These users will successfully clear __GFP_DMA and __GFP_HIGHMEM
no matter what values GFP_DMA and GFP_HIGHMEM have; the only problem will
be if someone calls them with a zone type they're not expecting (eg DMA32
for the first one or DMA for the second; or MOVABLE for either of them).
The thing is, they're already buggy in those circumstances.
> */
> -#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)
> #define __GFP_MOVABLE ((__force gfp_t)___GFP_MOVABLE) /* ZONE_MOVABLE allowed */
[...]
> 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;
>
> - z = (GFP_ZONE_TABLE >> (bit * GFP_ZONES_SHIFT)) &
> - ((1 << GFP_ZONES_SHIFT) - 1);
> - VM_BUG_ON((GFP_ZONE_BAD >> bit) & 1);
> + if (z > OPT_ZONE_HIGHMEM) {
> + z = OPT_ZONE_HIGHMEM +
> + !!((__force unsigned int)flags & ___GFP_MOVABLE);
> + }
> return z;
> }
How about:
+#define __GFP_HIGHMEM ((__force gfp_t)OPT_ZONE_HIGHMEM ^ ZONE_NORMAL)
-#define __GFP_MOVABLE ((__force gfp_t)___GFP_MOVABLE) /* ZONE_MOVABLE allowed */
+#define __GFP_MOVABLE ((__force gfp_t)ZONE_MOVABLE ^ ZONE_NORMAL | \
+ ___GFP_MOVABLE)
Then I think you can just make it:
static inline enum zone_type gfp_zone(gfp_t flags)
{
return ((__force int)flags & ___GFP_ZONE_MASK) ^ ZONE_NORMAL;
}
> @@ -370,42 +368,15 @@ static inline bool gfpflags_allow_blocking(const gfp_t gfp_flags)
> #error GFP_ZONES_SHIFT too large to create GFP_ZONE_TABLE integer
> #endif
You should be able to delete GFP_ZONES_SHIFT too.
next prev parent reply other threads:[~2018-05-06 18:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 6:52 [PATCH 0/3] Some fixes for mm code optimization Huaisheng Ye
[not found] ` <1525416729-108201-4-git-send-email-yehs1@lenovo.com>
2018-05-04 13:18 ` [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages Michal Hocko
2018-05-05 2:10 ` [External] " Huaisheng HS1 Ye
2018-05-09 7:48 ` Michal Hocko
[not found] ` <1525416729-108201-3-git-send-email-yehs1@lenovo.com>
2018-05-04 13:35 ` [PATCH 2/3] include/linux/gfp.h: use unsigned int in gfp_zone Michal Hocko
2018-05-04 15:40 ` Matthew Wilcox
2018-05-04 17:50 ` [External] " Huaisheng HS1 Ye
2018-05-06 9:32 ` Huaisheng HS1 Ye
2018-05-06 13:48 ` Matthew Wilcox
2018-05-06 16:17 ` Huaisheng HS1 Ye
2018-05-06 18:55 ` Matthew Wilcox [this message]
2018-05-07 17:16 ` Huaisheng HS1 Ye
2018-05-07 18:44 ` Matthew Wilcox
2018-05-07 21:25 ` David Sterba
2018-05-08 0:25 ` Matthew Wilcox
2018-05-09 9:36 ` David Sterba
2018-05-15 11:54 ` Matthew Wilcox
2018-05-21 17:06 ` David Sterba
2018-05-09 14:57 ` Huaisheng HS1 Ye
2018-05-08 0:25 ` 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=20180506185532.GA13604@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=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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