public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: Simplify the bio cloning implementation
Date: Thu, 28 Jun 2018 08:08:47 +0800	[thread overview]
Message-ID: <20180628000846.GF7583@ming.t460p> (raw)
In-Reply-To: <6d9bb0d0-52fd-8f16-6443-dcd8867bdb7c@wdc.com>

On Wed, Jun 27, 2018 at 04:55:20PM -0700, Bart Van Assche wrote:
> On 06/27/18 16:21, Ming Lei wrote:
> > What we need to do is to only copy the 1st bvec for WRITE_SAME, your patch
> > changes to copy (bio->bi_iter.bi_size / block size) bvecs, then memory corruption
> > may be triggered. So bio_for_each_segment() can't be used here.
> 
> Has it been considered to use memcpy() to copy the bi_vcnt bio_vecs instead
> of using bio_for_each_segment() in bio_clone_bioset()? That will in this
> context probably be even faster than using bio_for_each_segment().

After immutable bvec is introduced:

1) there is little chance in which bvec table need to copy, so performance
may not be a issue, as you see, bio_clone_bioset() is going to die now.

2) bi_vcnt/bi_io_vec can't be used directly on fast-cloned bio

2) code is simplified a lot by using iterator helper since bio can be
advanced in unit of byte. In theory, we may cook a special helper to
speed up the copy, but still depends on use cases.

thanks,
Ming

      reply	other threads:[~2018-06-28  0:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 22:26 [PATCH] block: Simplify the bio cloning implementation Bart Van Assche
2018-06-27  1:13 ` Ming Lei
2018-06-27 17:48   ` Bart Van Assche
2018-06-27 23:20     ` Ming Lei
2018-06-27 23:55       ` Bart Van Assche
2018-06-28  0:08         ` Ming Lei [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=20180628000846.GF7583@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bart.vanassche@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-block@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