From: Jan Vesely <jvesely@redhat.com>
To: Jens Axboe <axboe@kernel.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org
Cc: Kent Overstreet <koverstreet@google.com>,
Rob Evers <revers@redhat.com>, Tomas Henzl <thenzl@redhat.com>,
Nikola Pajkovsky <npajkovs@redhat.com>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Don Howard <dhoward@redhat.com>
Subject: [PATCH v4 2/2] block: modify __bio_add_page check to accept pages that don't start a new segment
Date: Fri, 12 Jul 2013 17:52:23 +0200 [thread overview]
Message-ID: <1373644343-6671-3-git-send-email-jvesely@redhat.com> (raw)
In-Reply-To: <1373644343-6671-1-git-send-email-jvesely@redhat.com>
From: Jan Vesely <jvesely@redhat.com>
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their buffers
to potentially require exactly max segments and multiple pages in the last
segment. This patch modifies the check to allow pages that can be merged into
the last segment.
Fixes EBUSY failures when using large tape block size in high
memory fragmentation condition. This regression was introduced by commit
46081b166415acb66d4b3150ecefcd9460bb48a1
st: Increase success probability in driver buffer allocation
Signed-off-by: Jan Vesely <jvesely@redhat.com>
CC: Alexander Viro <viro@zeniv.linux.org.uk>
CC: James Bottomley <James.Bottomley@hansenpartnership.com>
CC: Jens Axboe <axboe@kernel.dk>
CC: Kent Overstreet <koverstreet@google.com>
CC: Rob Evers <revers@redhat.com>
CC: Tomas Henzl <thenzl@redhat.com>
CC: Nikola Pajkovsky <npajkovs@redhat.com>
CC: Kai Makisara <Kai.Makisara@kolumbus.fi>
CC: linux-scsi@vger.kernel.org
CC: linux-fsdevel@vger.kernel.org
---
fs/bio.c | 30 +++++++++++++++++++-----------
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/fs/bio.c b/fs/bio.c
index 94bbc04..ba64e99 100644
--- a/fs/bio.c
+++ b/fs/bio.c
@@ -603,7 +603,6 @@ static int __bio_add_page(struct request_queue *q, struct bio *bio, struct page
*page, unsigned int len, unsigned int offset,
unsigned short max_sectors)
{
- int retried_segments = 0;
struct bio_vec *bvec;
/*
@@ -654,18 +653,12 @@ static int __bio_add_page(struct request_queue *q, struct bio *bio, struct page
return 0;
/*
- * we might lose a segment or two here, but rather that than
- * make this too complex.
+ * The first part of the segment count check,
+ * reduce segment count if possible
*/
-
- while (bio->bi_phys_segments >= queue_max_segments(q)) {
-
- if (retried_segments)
- return 0;
-
- retried_segments = 1;
+ if (bio->bi_phys_segments >= queue_max_segments(q))
blk_recount_segments(q, bio);
- }
+
/*
* setup the new entry, we might clear it again later if we
@@ -677,6 +670,21 @@ static int __bio_add_page(struct request_queue *q, struct bio *bio, struct page
bvec->bv_offset = offset;
/*
+ * the other part of the segment count check, allow mergeable pages.
+ * BIO_SEG_VALID flag is cleared below
+ */
+ if ((bio->bi_phys_segments > queue_max_segments(q)) ||
+ ((bio->bi_phys_segments == queue_max_segments(q)) &&
+ !bvec_mergeable(q, __BVEC_END(bio), bvec,
+ bio->bi_seg_back_size))) {
+ bvec->bv_page = NULL;
+ bvec->bv_len = 0;
+ bvec->bv_offset = 0;
+ return 0;
+ }
+
+
+ /*
* if queue has other restrictions (eg varying max sector size
* depending on offset), it can specify a merge_bvec_fn in the
* queue to get further control
--
1.8.3.1
next prev parent reply other threads:[~2013-07-12 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 15:52 [PATCH v4 0/2] block: Allow merging of tail pages into the last segment Jan Vesely
2013-07-12 15:52 ` [PATCH v4 1/2] block: factor out vector mergeable decision to a helper function Jan Vesely
2013-07-12 15:52 ` Jan Vesely [this message]
2013-07-26 10:41 ` [PATCH v4 0/2] block: Fix regression since 46081b166415acb66d4b3150ecefcd9460bb48a1 (was: Allow merging of tail pages into the last segment) Jan Vesely
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=1373644343-6671-3-git-send-email-jvesely@redhat.com \
--to=jvesely@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=axboe@kernel.dk \
--cc=dhoward@redhat.com \
--cc=koverstreet@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=npajkovs@redhat.com \
--cc=revers@redhat.com \
--cc=thenzl@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).