All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] scsi: sd: provide a new module parameter to set whether SCSI disks support WRITE_SAME_16 by default
@ 2020-01-19 14:13 AlexChen
  2020-01-19 19:36 ` Bart Van Assche
  0 siblings, 1 reply; 4+ messages in thread
From: AlexChen @ 2020-01-19 14:13 UTC (permalink / raw)
  To: jejb, martin.petersen; +Cc: linux-scsi, zhengchuan, jiangyiwen, robin.yb

When the SCSI device is initialized, check whether it supports
WRITE_SAME_16 or WRITE_SAME_10 in the sd_read_write_same(). If
the back-end storage device does not support queries, it will not set
sdkp->ws16 as 1.

When the WRITE_SAME io is issued through the blkdev_issue_write_same(),
the WRITE_SAME type is set to WRITE_SAME_10 by default in the
sd_setup_write_same_cmnd() since of "sdkp->ws16=0". If the storage device
does not support WRITE_SAME_10, then the SCSI device is set to not support
WRITE_SAME.

Currently, some storage devices do not provide queries for
WRITE_SAME_16/WRITE_SAME_10 support, but they do support WRITE_SAME_16 and
do not support WRITE_SAME_10. So in order for these devices to use
WRITE_SAME, we need a new module parameter to set whether SCSI disks
support WRITE_SAME_16 by default.

Signed-off-by: AlexChen <alex.chen@huawei.com>
---
 drivers/scsi/sd.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 4f7e7b607..ff368701d 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -104,6 +104,9 @@ MODULE_ALIAS_SCSI_DEVICE(TYPE_ZBC);
 #define SD_MINORS	0
 #endif

+static int sd_default_support_ws16;
+module_param(sd_default_support_ws16, int, 0644);
+
 static void sd_config_discard(struct scsi_disk *, unsigned int);
 static void sd_config_write_same(struct scsi_disk *);
 static int  sd_revalidate_disk(struct gendisk *);
@@ -3014,7 +3017,8 @@ static void sd_read_write_same(struct scsi_disk *sdkp, unsigned char *buffer)
 			sdev->no_write_same = 1;
 	}

-	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1)
+	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1 ||
+			sd_default_support_ws16)
 		sdkp->ws16 = 1;

 	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME) == 1)
-- 2.19.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] scsi: sd: provide a new module parameter to set whether SCSI disks support WRITE_SAME_16 by default
  2020-01-19 14:13 [PATCH] scsi: sd: provide a new module parameter to set whether SCSI disks support WRITE_SAME_16 by default AlexChen
@ 2020-01-19 19:36 ` Bart Van Assche
  2020-01-20  7:32   ` AlexChen
  2020-01-21  0:01   ` Martin K. Petersen
  0 siblings, 2 replies; 4+ messages in thread
From: Bart Van Assche @ 2020-01-19 19:36 UTC (permalink / raw)
  To: AlexChen, jejb, martin.petersen
  Cc: linux-scsi, zhengchuan, jiangyiwen, robin.yb

On 2020-01-19 06:13, AlexChen wrote:
> When the SCSI device is initialized, check whether it supports
> WRITE_SAME_16 or WRITE_SAME_10 in the sd_read_write_same(). If
> the back-end storage device does not support queries, it will not set
> sdkp->ws16 as 1.
> 
> When the WRITE_SAME io is issued through the blkdev_issue_write_same(),
> the WRITE_SAME type is set to WRITE_SAME_10 by default in the
> sd_setup_write_same_cmnd() since of "sdkp->ws16=0". If the storage device
> does not support WRITE_SAME_10, then the SCSI device is set to not support
> WRITE_SAME.
> 
> Currently, some storage devices do not provide queries for
> WRITE_SAME_16/WRITE_SAME_10 support, but they do support WRITE_SAME_16 and
> do not support WRITE_SAME_10. So in order for these devices to use
> WRITE_SAME, we need a new module parameter to set whether SCSI disks
> support WRITE_SAME_16 by default.
> 
> Signed-off-by: AlexChen <alex.chen@huawei.com>
> ---
>  drivers/scsi/sd.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 4f7e7b607..ff368701d 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -104,6 +104,9 @@ MODULE_ALIAS_SCSI_DEVICE(TYPE_ZBC);
>  #define SD_MINORS	0
>  #endif
> 
> +static int sd_default_support_ws16;
> +module_param(sd_default_support_ws16, int, 0644);
> +
>  static void sd_config_discard(struct scsi_disk *, unsigned int);
>  static void sd_config_write_same(struct scsi_disk *);
>  static int  sd_revalidate_disk(struct gendisk *);
> @@ -3014,7 +3017,8 @@ static void sd_read_write_same(struct scsi_disk *sdkp, unsigned char *buffer)
>  			sdev->no_write_same = 1;
>  	}
> 
> -	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1)
> +	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1 ||
> +			sd_default_support_ws16)
>  		sdkp->ws16 = 1;
> 
>  	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME) == 1)

Should this be fixed using the quirk mechanism instead of introducing a
new kernel module parameter? Kernel module parameters apply to all SCSI
disk devices irrespective of their vendor and model. The quirk mechanism
can be used to introduce special behavior for certain disk models and
types. See also the output of the following grep command:

$ git grep -nH '& BLIST'

Bart.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] scsi: sd: provide a new module parameter to set whether SCSI disks support WRITE_SAME_16 by default
  2020-01-19 19:36 ` Bart Van Assche
@ 2020-01-20  7:32   ` AlexChen
  2020-01-21  0:01   ` Martin K. Petersen
  1 sibling, 0 replies; 4+ messages in thread
From: AlexChen @ 2020-01-20  7:32 UTC (permalink / raw)
  To: Bart Van Assche
  Cc: jejb, martin.petersen, linux-scsi, zhengchuan, jiangyiwen, robin.yb

On 2020/1/20 3:36, Bart Van Assche wrote:
> On 2020-01-19 06:13, AlexChen wrote:
>> When the SCSI device is initialized, check whether it supports
>> WRITE_SAME_16 or WRITE_SAME_10 in the sd_read_write_same(). If
>> the back-end storage device does not support queries, it will not set
>> sdkp->ws16 as 1.
>>
>> When the WRITE_SAME io is issued through the blkdev_issue_write_same(),
>> the WRITE_SAME type is set to WRITE_SAME_10 by default in the
>> sd_setup_write_same_cmnd() since of "sdkp->ws16=0". If the storage device
>> does not support WRITE_SAME_10, then the SCSI device is set to not support
>> WRITE_SAME.
>>
>> Currently, some storage devices do not provide queries for
>> WRITE_SAME_16/WRITE_SAME_10 support, but they do support WRITE_SAME_16 and
>> do not support WRITE_SAME_10. So in order for these devices to use
>> WRITE_SAME, we need a new module parameter to set whether SCSI disks
>> support WRITE_SAME_16 by default.
>>
>> Signed-off-by: AlexChen <alex.chen@huawei.com>
>> ---
>>  drivers/scsi/sd.c | 6 +++++-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
>> index 4f7e7b607..ff368701d 100644
>> --- a/drivers/scsi/sd.c
>> +++ b/drivers/scsi/sd.c
>> @@ -104,6 +104,9 @@ MODULE_ALIAS_SCSI_DEVICE(TYPE_ZBC);
>>  #define SD_MINORS	0
>>  #endif
>>
>> +static int sd_default_support_ws16;
>> +module_param(sd_default_support_ws16, int, 0644);
>> +
>>  static void sd_config_discard(struct scsi_disk *, unsigned int);
>>  static void sd_config_write_same(struct scsi_disk *);
>>  static int  sd_revalidate_disk(struct gendisk *);
>> @@ -3014,7 +3017,8 @@ static void sd_read_write_same(struct scsi_disk *sdkp, unsigned char *buffer)
>>  			sdev->no_write_same = 1;
>>  	}
>>
>> -	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1)
>> +	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1 ||
>> +			sd_default_support_ws16)
>>  		sdkp->ws16 = 1;
>>
>>  	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME) == 1)
> 
> Should this be fixed using the quirk mechanism instead of introducing a
> new kernel module parameter? Kernel module parameters apply to all SCSI
> disk devices irrespective of their vendor and model. The quirk mechanism
> can be used to introduce special behavior for certain disk models and
> types. See also the output of the following grep command:
> 
> $ git grep -nH '& BLIST'
> 
> Bart.
> 
Thanks for your reply.
I will try to fix the problem by the way you suggested above.

Thanks
Alex
> 
> .
> 



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] scsi: sd: provide a new module parameter to set whether SCSI disks support WRITE_SAME_16 by default
  2020-01-19 19:36 ` Bart Van Assche
  2020-01-20  7:32   ` AlexChen
@ 2020-01-21  0:01   ` Martin K. Petersen
  1 sibling, 0 replies; 4+ messages in thread
From: Martin K. Petersen @ 2020-01-21  0:01 UTC (permalink / raw)
  To: Bart Van Assche
  Cc: AlexChen, jejb, martin.petersen, linux-scsi, zhengchuan,
	jiangyiwen, robin.yb


Bart,

>> +	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME_16) == 1 ||
>> +			sd_default_support_ws16)
>>  		sdkp->ws16 = 1;
>> 
>>  	if (scsi_report_opcode(sdev, buffer, SD_BUF_SIZE, WRITE_SAME) == 1)
>
> Should this be fixed using the quirk mechanism instead of introducing a
> new kernel module parameter? Kernel module parameters apply to all SCSI
> disk devices irrespective of their vendor and model. The quirk mechanism
> can be used to introduce special behavior for certain disk models and
> types.

Yes, this should definitely be a blacklist option. Although I'd
obviously encourage the vendor to implement RSOC instead of working
around this in the kernel.

-- 
Martin K. Petersen	Oracle Linux Engineering

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-01-21  0:01 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-19 14:13 [PATCH] scsi: sd: provide a new module parameter to set whether SCSI disks support WRITE_SAME_16 by default AlexChen
2020-01-19 19:36 ` Bart Van Assche
2020-01-20  7:32   ` AlexChen
2020-01-21  0:01   ` Martin K. Petersen

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.