summaryrefslogtreecommitdiffstats
path: root/block/bio.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2016-03-11 17:34:53 +0100
committerJens Axboe <axboe@fb.com>2016-03-14 08:55:25 -0600
commit2b885517110cbe8724fef30363778b6284d0a428 (patch)
tree609935ecfa54b2e31752f375ec1dfb46cf3fca71 /block/bio.c
parentba8c6967b7391aab8fa562611fe637a57850b4aa (diff)
downloadlinux-2b885517110cbe8724fef30363778b6284d0a428.tar.bz2
block: bio_remaining_done() isn't unlikely
We use bio chaining during most I/Os these days due to the delayed bio splitting. Additionally XFS will start using it, and there is a pending direct I/O rewrite also making heavy use for it. Don't pretend it's always unlikely, and let the branch predictor do it's job instead. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block/bio.c')
-rw-r--r--block/bio.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/block/bio.c b/block/bio.c
index e4682ec11fcd..0fde6e0e81f2 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -1746,7 +1746,7 @@ static inline bool bio_remaining_done(struct bio *bio)
void bio_endio(struct bio *bio)
{
again:
- if (unlikely(!bio_remaining_done(bio)))
+ if (!bio_remaining_done(bio))
return;
/*