From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
Dmitry Monakhov <dmonakhov@openvz.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Hannes Reinecke <hare@suse.com>,
linux-block@vger.kernel.org
Subject: Re: bvec_iter rewind API
Date: Tue, 4 Sep 2018 20:46:25 +0200 [thread overview]
Message-ID: <20180904184625.GA1782@lst.de> (raw)
In-Reply-To: <20180830112414.GA8186@ming.t460p>
On Thu, Aug 30, 2018 at 07:24:15PM +0800, Ming Lei wrote:
> I agree, and it isn't good to introduce extra update of .bi_done in fast path
> too, and it just makes things complicated in concept.
>
> Maybe we can do the following way, and looks it works in scsi_debug/dix
> test.
Can you send that as a proper patch series?
prev parent reply other threads:[~2018-09-04 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 23:33 bvec_iter rewind API Kent Overstreet
2018-08-29 14:56 ` Jens Axboe
2018-08-30 11:24 ` Ming Lei
2018-09-04 18:46 ` Christoph Hellwig [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=20180904184625.GA1782@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dmonakhov@openvz.org \
--cc=hare@suse.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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