linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Vesely <jvesely@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] block: modify __bio_add_page check to accept pages that don't start a new segment
Date: Thu, 07 Mar 2013 12:23:13 +0100	[thread overview]
Message-ID: <513878A1.3020701@redhat.com> (raw)
In-Reply-To: <5125DB22.7020901@redhat.com>

Hi Jens,

I have added you to cc, I'm not sure who to bug to get this patch 
merged.

thanks,
Jan Vesely

On Thu 21 Feb 2013 09:30:26 CET, Jan Vesely wrote:
> 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.
>
> This change fixes EBUSY failures when using large (1mb) tape block size in high
> memory fragmentation condition.
>
> Signed-off-by: Jan Vesely <jvesely@redhat.com>
> ---
>  fs/bio.c |   26 ++++++++++++++++----------
>  1 files changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/fs/bio.c b/fs/bio.c
> index b96fc6c..02efbd5 100644
> --- a/fs/bio.c
> +++ b/fs/bio.c
> @@ -500,7 +500,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;
>
>      /*
> @@ -551,18 +550,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.
> +     * prepare 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
> @@ -572,6 +565,19 @@ static int __bio_add_page(struct request_queue *q, struct
> bio *bio, struct page
>      bvec->bv_page = page;
>      bvec->bv_len = len;
>      bvec->bv_offset = offset;
> +
> +    /*
> +     * the other part of the segment count check, allow mergeable pages
> +     */
> +    if ((bio->bi_phys_segments > queue_max_segments(q)) ||
> +        ( (bio->bi_phys_segments == queue_max_segments(q)) &&
> +        !BIOVEC_PHYS_MERGEABLE(bvec - 1, bvec))) {
> +            bvec->bv_page = NULL;
> +            bvec->bv_len = 0;
> +            bvec->bv_offset = 0;
> +            return 0;
> +    }
> +
>
>      /*
>       * if queue has other restrictions (eg varying max sector size

--
Jan Vesely <jvesely@redhat.com>

  reply	other threads:[~2013-03-07 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21  8:30 [PATCH] block: modify __bio_add_page check to accept pages that don't start a new segment Jan Vesely
2013-03-07 11:23 ` Jan Vesely [this message]
2013-03-25 13:09   ` Jan Vesely
2013-03-25 13:31     ` Jens Axboe

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=513878A1.3020701@redhat.com \
    --to=jvesely@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).