From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "hch@infradead.org" <hch@infradead.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
Subject: Re: [PATCH 0/2] scsi: sd: use READ/WRITE/SYNC (16) commands per ZBC
Date: Thu, 10 Nov 2022 02:20:09 +0000 [thread overview]
Message-ID: <20221110022009.xdfmlpdpw2kyu32x@shindev> (raw)
In-Reply-To: <Y2ue2rZzf74/1V+U@infradead.org>
On Nov 09, 2022 / 04:36, Christoph Hellwig wrote:
> What is the point in relaxing this? Every modern device better support
> 16 byte commands even if they aren't strictly required for host aware
> devices.
My point was to make the check strictly follow the ZBC spec. But now I see that
it's the better to keep enforcing 16 byte commands to host-aware devices. I will
drop the first patch and revise the second patch to enforce SYNC 16 on both
host-aware and host-managed devices.
--
Shin'ichiro Kawasaki
next prev parent reply other threads:[~2022-11-10 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 2:59 [PATCH 0/2] scsi: sd: use READ/WRITE/SYNC (16) commands per ZBC Shin'ichiro Kawasaki
2022-11-09 2:59 ` [PATCH 1/2] scsi: sd_zbc: do not enforce READ/WRITE (16) on host-aware devices Shin'ichiro Kawasaki
2022-11-09 5:17 ` Damien Le Moal
2022-11-09 2:59 ` [PATCH 2/2] scsi: sd: enforce SYNCHRONIZE CACHE (16) on host-managed devices Shin'ichiro Kawasaki
2022-11-09 5:18 ` Damien Le Moal
2022-11-09 12:36 ` [PATCH 0/2] scsi: sd: use READ/WRITE/SYNC (16) commands per ZBC Christoph Hellwig
2022-11-10 2:20 ` Shinichiro Kawasaki [this message]
2022-11-10 8:19 ` hch
2022-11-10 8:31 ` Damien Le Moal
2022-11-14 10:58 ` Shinichiro Kawasaki
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=20221110022009.xdfmlpdpw2kyu32x@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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