Re: [PATCH] megaraid_sas: Re-enable WRITE SAME

2018-02-27 Thread Martin K. Petersen
Shivasharan, > So my understanding is when driver sets no_write_same flag, it is only > disabling BLKZEROOUT/write_zeroes requests from using WRITE SAME > command. Instead individual writes are sent to zero the blocks (if > BLKDEV_ZERO_NOFALLBACK flag is not set). Correct. > Our inhouse driver

RE: [PATCH] megaraid_sas: Re-enable WRITE SAME

2018-02-26 Thread Shivasharan Srikanteshwara
> -Original Message- > From: Martin K. Petersen [mailto:martin.peter...@oracle.com] > Sent: Thursday, February 22, 2018 9:52 AM > To: Shivasharan S > Cc: linux-scsi@vger.kernel.org; kashyap.de...@broadcom.com; > sumit.sax...@broadcom.com > Subject: Re: [PATCH] me

Re: [PATCH] megaraid_sas: Re-enable WRITE SAME

2018-02-21 Thread Martin K. Petersen
Hi Shivasharan! > For MegaRAID controller we want to support WRITE SAME for non-raid > volumes. Because of host wide "no_write_same = 1" settings, we are > not able to use provision mode. The no_write_same flag gates whether the WRITE SAME(10/16) commands are used to zero block ranges. It does

[PATCH] megaraid_sas: Re-enable WRITE SAME

2018-02-20 Thread Shivasharan S
Below commit disable WRITE SAME behavior via host template no_write_same settings for megaraid_sas driver. commit 54b2b50c20a6 ("[SCSI] Disable WRITE SAME for RAID and virtual host adapter drivers") For MegaRAID controller we want to support WRITE SAME for non-raid volumes. Because of host wide "