linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dmitri Monakhov <dmonakhov@openvz.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fix bio_add_page for non trivial merge_bvec_fn case
Date: Tue, 1 Jul 2008 09:14:00 +0200	[thread overview]
Message-ID: <20080701071359.GY20826@kernel.dk> (raw)
In-Reply-To: <20080630133739.fc4effec.akpm@linux-foundation.org>

On Mon, Jun 30 2008, Andrew Morton wrote:
> On Sun, 08 Jun 2008 19:45:08 +0400
> Dmitri Monakhov <dmonakhov@openvz.org> wrote:
> 
> > We have to properly decrease all related bio's counters, especially bi_size
> > in order to merge_bvec_fn return right result. Usually this result in
> > false merge rejects for two absolutely valid bio_vecs. This may cause 
> > significant performance penalty for example Itanium: page_size == 16k,
> > fs_block_size == 1k and block device is raid with small chunk_size.
> > 
> 
> Please cc Jens on BIO changes.
> 
> > ---
> >  fs/bio.c |   16 ++++++++++++----
> >  1 files changed, 12 insertions(+), 4 deletions(-)
> > 
> > diff --git a/fs/bio.c b/fs/bio.c
> > index 7856257..d713074 100644
> > --- a/fs/bio.c
> > +++ b/fs/bio.c
> > @@ -332,14 +332,21 @@ static int __bio_add_page(struct request_queue *q, struct bio *bio, struct page
> >  
> >  		if (page == prev->bv_page &&
> >  		    offset == prev->bv_offset + prev->bv_len) {
> > +			/* Temprory detacth last bio_vec. */
> 
> whoa, drunken speling.
> 
> > +			bio->bi_size -= prev->bv_len;
> > +			bio->bi_vcnt--;
> > +			bio->bi_phys_segments--;
> > +			bio->bi_hw_segments--;
> > +

This logic isn't quite right, the rules for what constitutes a new hw or
phys segment is not a 1:1 mapping with number of pages in the bio. How
about just dropping the segment decrement? The merge_bvec fn should not
care, and we'll retry and coalesce segment count if we get to the limit
anyway.

-- 
Jens Axboe


      reply	other threads:[~2008-07-01  7:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 15:45 [PATCH] fix bio_add_page for non trivial merge_bvec_fn case Dmitri Monakhov
2008-06-30 20:37 ` Andrew Morton
2008-07-01  7:14   ` Jens Axboe [this message]

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=20080701071359.GY20826@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmonakhov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).