public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: "hch@infradead.org" <hch@infradead.org>,
	Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Martin K . Petersen" <martin.petersen@oracle.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 17:31:02 +0900	[thread overview]
Message-ID: <797133cf-ed12-233e-8148-a08bf1261a35@opensource.wdc.com> (raw)
In-Reply-To: <Y2y0AhBCm+O4HoRg@infradead.org>

On 11/10/22 17:19, hch@infradead.org wrote:
> On Thu, Nov 10, 2022 at 02:20:09AM +0000, Shinichiro Kawasaki wrote:
>> 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.
> 
> We don't "enforce" anything.  We just don't send the legacy commands for
> devices that are guaranteed to be modern.  What is the advantage of
> ever sending 10 bytes commands (inluding SYNCHRONIZE CACHE) to a modern
> device?

The ZBC specs define SYNC 16 as optional while SYNC 10 is mandatory. So
the device may not support SYNC 16 and we would get an invalid opcode
error. For SYNC, no advantages between SYNC 10 and SYNC 16. Not even
sure why they both exist. The point here is making sure we use the one
that the drive MUST support. That is, SYNC 16 for host managed and SYNC
10 for host aware (but these likely all also support SYNC 16, but we
cannot be sure of it).

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2022-11-10  8:31 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
2022-11-10  8:19     ` hch
2022-11-10  8:31       ` Damien Le Moal [this message]
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=797133cf-ed12-233e-8148-a08bf1261a35@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=Dmitry.Fomichev@wdc.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=shinichiro.kawasaki@wdc.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