All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, Niklas Cassel <cassel@kernel.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH] scsi/sd_zbc: Use READ(10)/WRITE(10) for zoned UFS devices
Date: Thu, 29 Feb 2024 10:31:58 -0800	[thread overview]
Message-ID: <ecbc260c-1202-4b0f-bcc9-4886c85bf43c@kernel.org> (raw)
In-Reply-To: <eec0d0d1-9fe3-457f-8150-e5cbe19a9f23@acm.org>

On 2024/02/29 10:05, Bart Van Assche wrote:
> On 2/29/24 09:29, Damien Le Moal wrote:
>> On 2024/02/29 9:23, Bart Van Assche wrote:
>>> +	if (sdev->type == TYPE_ZBC) {
>>> +		/* READ16/WRITE16/SYNC16 is mandatory for ZBC devices */
>>> +		sdev->use_16_for_rw = 1;
>>> +		sdev->use_16_for_sync = 1;
>>
>> scsi_add_lun() sets use_10_for_rw to "1" so can we clear it to "0" here again
>> like was done in the sd_zbc.c hunk below that you removed ?
> Hi Damien,
> 
> Although it would be easy to make that change, will it cause any
> difference in behavior? sd_setup_read_write_cmnd() checks the value of 
> .use_16_for_rw before it checks the value of .use_10_for_rw. Hence, the
> value of .use_10_for_rw does not matter if .use_16_for_rw is set.

Yes, but I find that a little fragile and given that rw-10 causes problems with
ZBC, I prefer to make it very explicit that the 10B command variants should not
be used.


-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2024-02-29 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 17:23 [PATCH] scsi/sd_zbc: Use READ(10)/WRITE(10) for zoned UFS devices Bart Van Assche
2024-02-29 17:29 ` Damien Le Moal
2024-02-29 18:05   ` Bart Van Assche
2024-02-29 18:31     ` Damien Le Moal [this message]
2024-02-29 18:54       ` Bart Van Assche
2024-02-29 19:58         ` Damien Le Moal
2024-02-29 20:05           ` Bart Van Assche
2024-02-29 22:07             ` Bart Van Assche
2024-02-29 22:16               ` Damien Le Moal
2024-02-29 22:39                 ` Bart Van Assche
2024-02-29 22:45                   ` Damien Le Moal
2024-02-29 23:25                     ` Bart Van Assche
2024-02-29 23:53                       ` Damien Le Moal
2024-03-01 13:09 ` Christoph Hellwig

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=ecbc260c-1202-4b0f-bcc9-4886c85bf43c@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=cassel@kernel.org \
    --cc=jejb@linux.ibm.com \
    --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 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.