[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1396532277-14226-1-git-send-email-nasa4836@gmail.com>
Date: Thu, 3 Apr 2014 21:37:57 +0800
From: Jianyu Zhan <nasa4836@...il.com>
To: jack@...e.cz
Cc: axboe@...nel.dk, linux-kernel@...r.kernel.org,
viro@...iv.linux.org.uk, Jianyu Zhan <nasa4836@...il.com>
Subject: Re: [PATCH] blkdev: use an efficient way to check merge flags
Hi, Jan,
I've just renewed the patch as you suggusted. Actually it isn't quite
performance sensitive, but the point is one less branch leads to
less penalty caused by branch prediction failure. Ok, this may be
way too paranoid.:-)
A bitwise flag comparison could be done using a more efficient bit-ops
way, by mimicking GCC logic of optimizing such bitwise comparison.
Signed-off-by: Jianyu Zhan <nasa4836@...il.com>
---
include/linux/blkdev.h | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 1e1fa3f..f2b79fc 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -655,16 +655,18 @@ static inline bool rq_mergeable(struct request *rq)
static inline bool blk_check_merge_flags(unsigned int flags1,
unsigned int flags2)
{
- if ((flags1 & REQ_DISCARD) != (flags2 & REQ_DISCARD))
- return false;
-
- if ((flags1 & REQ_SECURE) != (flags2 & REQ_SECURE))
- return false;
-
- if ((flags1 & REQ_WRITE_SAME) != (flags2 & REQ_WRITE_SAME))
- return false;
-
- return true;
+ /*
+ * Check whether all tree flags are the same in both
+ * flags.
+ *
+ * Replace original three-if's comparision with a
+ * more efficient method, by mimicking the GCC logic of
+ * optimizing such bitwise comparion. This makes GCC
+ * to spit out most compact and least brach code.
+ */
+ return ((flags1 ^ flags2) &
+ (REQ_DISCARD | REQ_SECURE | REQ_WRITE_SAME))
+ == 0;
}
static inline bool blk_write_same_mergeable(struct bio *a, struct bio *b)
--
1.9.0.GIT
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists