From: Michal Hocko <mhocko@kernel.org>
To: Igor Stoppa <igor.stoppa@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: namhyung@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Question on ___GFP_NOLOCKDEP - Was: Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks
Date: Thu, 27 Apr 2017 15:35:23 +0200 [thread overview]
Message-ID: <20170427133523.GG4706@dhcp22.suse.cz> (raw)
In-Reply-To: <9929419e-c22e-2a9f-a8a6-ad98d5a9da06@huawei.com>
On Thu 27-04-17 15:16:47, Igor Stoppa wrote:
> On 26/04/17 18:29, Igor Stoppa wrote:
>
> > On 26/04/17 17:47, Michal Hocko wrote:
>
> [...]
>
> >> Also the current mm tree has ___GFP_NOLOCKDEP which is not addressed
> >> here so I suspect you have based your change on the Linus tree.
>
> > I used your tree from kernel.org
>
> I found it, I was using master, instead of auto-latest (is it correct?)
yes
> But now I see something that I do not understand (apologies if I'm
> asking something obvious).
>
> First there is:
>
> [...]
> #define ___GFP_WRITE 0x800000u
> #define ___GFP_KSWAPD_RECLAIM 0x1000000u
> #ifdef CONFIG_LOCKDEP
> #define ___GFP_NOLOCKDEP 0x4000000u
> #else
> #define ___GFP_NOLOCKDEP 0
> #endif
>
> Then:
>
> /* Room for N __GFP_FOO bits */
> #define __GFP_BITS_SHIFT (25 + IS_ENABLED(CONFIG_LOCKDEP))
>
>
>
> Shouldn't it be either:
> ___GFP_NOLOCKDEP 0x2000000u
Yes it should. At the time when this patch was written this value was
used. Later I've removed __GFP_OTHER by 41b6167e8f74 ("mm: get rid of
__GFP_OTHER_NODE") and forgot to refresh this one. Thanks for noticing
this.
Andrew, could you fold the following in please?
---
>From 8dc9c917af215f659bb990fa48ae7b4753027c19 Mon Sep 17 00:00:00 2001
From: Michal Hocko <mhocko@suse.com>
Date: Thu, 27 Apr 2017 15:28:10 +0200
Subject: [PATCH] lockdep-allow-to-disable-reclaim-lockup-detection-fix
Igor Stoppa has noticed that __GFP_NOLOCKDEP can use a lower bit. At the
time lockdep-allow-to-disable-reclaim-lockup-detection was written we
still had __GFP_OTHER_NODE but I have removed it in 41b6167e8f74 ("mm:
get rid of __GFP_OTHER_NODE") and forgot to lower the bit value.
Signed-off-by: Michal Hocko <mhocko@suse.com>
---
include/linux/gfp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/gfp.h b/include/linux/gfp.h
index 2b1a44f5bdb6..a89d37e8b387 100644
--- a/include/linux/gfp.h
+++ b/include/linux/gfp.h
@@ -41,7 +41,7 @@ struct vm_area_struct;
#define ___GFP_WRITE 0x800000u
#define ___GFP_KSWAPD_RECLAIM 0x1000000u
#ifdef CONFIG_LOCKDEP
-#define ___GFP_NOLOCKDEP 0x4000000u
+#define ___GFP_NOLOCKDEP 0x2000000u
#else
#define ___GFP_NOLOCKDEP 0
#endif
--
2.11.0
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-04-27 13:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 13:35 [PATCH 0/1] mm: Improve consistency of ___GFP_xxx masks Igor Stoppa
2017-04-26 13:35 ` [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks Igor Stoppa
2017-04-26 14:47 ` Michal Hocko
2017-04-26 15:29 ` Igor Stoppa
2017-04-27 12:16 ` Question on ___GFP_NOLOCKDEP - Was: " Igor Stoppa
2017-04-27 13:35 ` Michal Hocko [this message]
2017-05-10 15:24 ` Vlastimil Babka
2017-04-27 12:18 ` Igor Stoppa
2017-04-27 13:41 ` Michal Hocko
2017-04-27 14:06 ` Igor Stoppa
2017-04-28 7:40 ` Michal Hocko
2017-04-28 7:43 ` Igor Stoppa
2017-04-28 8:13 ` Igor Stoppa
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=20170427133523.GG4706@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=igor.stoppa@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=namhyung@kernel.org \
/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).