From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-ide@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: ZBC_IN command translation
Date: Wed, 7 Jun 2017 23:55:54 -0700 [thread overview]
Message-ID: <20170608065553.GA14568@infradead.org> (raw)
In-Reply-To: <8b223c09-81ff-19dd-fe32-63711c79b9cb@wdc.com>
On Thu, Jun 08, 2017 at 09:18:39AM +0900, Damien Le Moal wrote:
> So I am limiting support in target to the passthrough SCSI (pscsi)
> backstore type (and will also add a user emulation backstore). Fixes
> needed in pscsi are rather trivial, but the block layer is not involved
> at the highest level as scsi commands are simply passed along through
> requests. Hence the ZBC/ZAC translation problem showing up.
Bah, don't do that. Passthrough backends are a nightmare in so many
ways and I really prefer to not see them spread.
>
> I could work on completing support for ZBC at the block layer API:
> 1) Add REQ_OP_ZONE_OPEN/CLOSE/FINISH, with corresponding
> blkdev_issue_xxx functions
Or just emulate them.
> 2) Add more queue attributes and corresponding files in sysfs for the
> zoned block device characteristics
> 3) Fix sd.c to support the new REQ_OP_ZONE_xxx
> 4) Add corresponding user ioctls for OPEN/CLOSE/FINISH
What is the practical use cae for that?
next prev parent reply other threads:[~2017-06-08 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:03 ZBC_IN command translation Damien Le Moal
2017-06-07 9:07 ` Christoph Hellwig
2017-06-07 9:11 ` Damien Le Moal
2017-06-07 13:24 ` Christoph Hellwig
2017-06-08 0:18 ` Damien Le Moal
2017-06-08 6:55 ` Christoph Hellwig [this message]
2017-06-08 8:27 ` 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=20170608065553.GA14568@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=hare@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tj@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