From: Mike Snitzer <snitzer@redhat.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
dm-devel@redhat.com, Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH 0/4] dm: zoned block device fixes
Date: Thu, 8 Jun 2017 16:21:47 -0400 [thread overview]
Message-ID: <20170608202146.GB6747@redhat.com> (raw)
In-Reply-To: <9749b12d-e232-5386-0894-511bb45758e7@wdc.com>
On Mon, Jun 05 2017 at 6:48am -0400,
Damien Le Moal <damien.lemoal@wdc.com> wrote:
> I did address some of the "FIXME" notes you added. The main one is the
> BIO cloning in the I/O path. I removed most of that and added a .end_io
> method for completion processing. The only place were I do not see how
> to remove the call to bio_clone() is during read BIO processing: since a
> read BIO may end up being split between buffer zone, sequential zone and
> simple buffer zero-out, fragmentation of the read BIO is sometimes
> necessary and so need a clone.
So shouldn't it be possible to not allow a given bio to cross zone
boundaries by using dm_accept_partial_bio()?
Like you're already doing in dmz_map() actually... so why do you need to
account for crossing zone boundaries on read later on in
dmz_submit_read_bio()?
Is it that these zones aren't easily known up front (in dmz_map)?
Mike
next prev parent reply other threads:[~2017-06-08 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 10:23 [PATCH 0/4] dm: zoned block device fixes Damien Le Moal
2017-05-29 10:23 ` [PATCH 1/4] dm: Fix mapping zone alignment check Damien Le Moal
2017-05-29 10:23 ` [PATCH 2/4] dm: Fix staking limits for zoned block device Damien Le Moal
2017-05-29 10:23 ` [PATCH 3/4] dm: Fix zoned block device model validation Damien Le Moal
2017-05-29 10:23 ` [PATCH 4/4] dm-zoned: Drive-managed zoned block device target Damien Le Moal
2017-05-30 20:20 ` [PATCH 0/4] dm: zoned block device fixes Mike Snitzer
2017-05-31 4:29 ` Damien Le Moal
2017-05-31 14:39 ` Mike Snitzer
2017-06-02 0:36 ` Mike Snitzer
2017-06-05 10:48 ` Damien Le Moal
2017-06-06 14:18 ` Mike Snitzer
2017-06-08 20:21 ` Mike Snitzer [this message]
2017-06-09 4:25 ` Damien Le Moal
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=20170608202146.GB6747@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bart.vanassche@sandisk.com \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.