From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] fix sparse warning from include/linux/mmzone.h
Date: Thu, 07 Feb 2008 12:52:23 -0800 [thread overview]
Message-ID: <1202417543.31361.5.camel@brick> (raw)
include/linux/mmzone.h:640:22: warning: potentially expensive pointer subtraction
The code in question was doing a pointer subtraction to find the index of
the zone argument in the node_zones array. This essentially boils down to:
((unsigned long)zone - (unsigned long)zone->zone_pgdat->node_zones)/sizeof(struct zone)
Which can be expensive if struct zone is not a power of two. Instead, just
calculate the offsets rather than the index in the array.
Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
---
This shows up > 30 times in an x86 allyesconfig, would be nice to get
rid of it and makes the code a little more efficient. I believe this
is correct, unless there is a subtlety I have missed.
include/linux/mmzone.h | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 8d8d197..cb07758 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -637,9 +637,12 @@ static inline int is_normal_idx(enum zone_type idx)
static inline int is_highmem(struct zone *zone)
{
#ifdef CONFIG_HIGHMEM
- int zone_idx = zone - zone->zone_pgdat->node_zones;
- return zone_idx == ZONE_HIGHMEM ||
- (zone_idx == ZONE_MOVABLE && zone_movable_is_highmem());
+ const int highmem_off = ZONE_HIGHMEM * sizeof(*zone);
+ const int movable_off = ZONE_MOVABLE * sizeof(*zone);
+
+ int zone_off = (unsigned long)zone - (unsigned long)zone->zone_pgdat->node_zones;
+ return zone_off == highmem_off ||
+ (zone_off == movable_off && zone_movable_is_highmem());
#else
return 0;
#endif
--
1.5.4.1219.g65b9
next reply other threads:[~2008-02-07 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 20:52 Harvey Harrison [this message]
2008-02-08 21:51 ` [PATCH] fix sparse warning from include/linux/mmzone.h Andrew Morton
2008-02-08 22:04 ` Linus Torvalds
2008-02-08 22:17 ` Harvey Harrison
2008-02-08 22:26 ` Ingo Molnar
2008-02-08 22:35 ` Linus Torvalds
2008-02-13 19:56 ` Harvey Harrison
2008-02-13 20:36 ` [PATCH] remove sparse warning for mmzone.h Harvey Harrison
2008-02-08 22:38 ` [PATCH] fix sparse warning from include/linux/mmzone.h Harvey Harrison
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=1202417543.31361.5.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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