From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Long Li <longli@microsoft.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"JBottomley@parallels.com" <JBottomley@parallels.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH] scsi:storvsc enable reading from VPD pages on SPC-2
Date: Thu, 11 Dec 2014 22:03:44 -0500 [thread overview]
Message-ID: <yq1vblhbmcv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <BL2PR03MB1324E11F2CB6EC2652C2F85CE620@BL2PR03MB132.namprd03.prod.outlook.com> (Long Li's message of "Wed, 10 Dec 2014 22:28:07 +0000")
>>>>> "Long" == Long Li <longli@microsoft.com> writes:
>> Handle the issues or handle WRITE SAME(10/16)?
Long> With this patch, the SCSI layer will be able to correctly send
Long> WRITE_SAME_16 to the Hyper-V host. It will not send WRITE_SAME_10:
Long> it has been disabled in the driver template. Do you want me to
Long> send another patch with these details?
no_write_same prevents us from attempting to use WRITE SAME(10/16) to
zero block ranges.
This is completely orthogonal to using the WRITE SAME(10/16) commands
with the UNMAP bit set to discard block ranges. The latter is controlled
by the logical block provisioning heuristics and is not affected by
no_write_same at all.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Long Li <longli@microsoft.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"JBottomley\@parallels.com" <JBottomley@parallels.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi:storvsc enable reading from VPD pages on SPC-2
Date: Thu, 11 Dec 2014 22:03:44 -0500 [thread overview]
Message-ID: <yq1vblhbmcv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <BL2PR03MB1324E11F2CB6EC2652C2F85CE620@BL2PR03MB132.namprd03.prod.outlook.com> (Long Li's message of "Wed, 10 Dec 2014 22:28:07 +0000")
>>>>> "Long" == Long Li <longli@microsoft.com> writes:
>> Handle the issues or handle WRITE SAME(10/16)?
Long> With this patch, the SCSI layer will be able to correctly send
Long> WRITE_SAME_16 to the Hyper-V host. It will not send WRITE_SAME_10:
Long> it has been disabled in the driver template. Do you want me to
Long> send another patch with these details?
no_write_same prevents us from attempting to use WRITE SAME(10/16) to
zero block ranges.
This is completely orthogonal to using the WRITE SAME(10/16) commands
with the UNMAP bit set to discard block ranges. The latter is controlled
by the logical block provisioning heuristics and is not affected by
no_write_same at all.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-12-12 3:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 8:38 [PATCH] scsi:storvsc enable reading from VPD pages on SPC-2 Long Li
2014-12-10 8:38 ` Long Li
2014-12-10 20:57 ` Sitsofe Wheeler
2014-12-10 20:57 ` Sitsofe Wheeler
2014-12-10 22:33 ` Long Li
2014-12-10 22:33 ` Long Li
2014-12-10 21:12 ` Martin K. Petersen
2014-12-10 21:12 ` Martin K. Petersen
2014-12-10 22:28 ` Long Li
2014-12-10 22:28 ` Long Li
2014-12-10 23:30 ` KY Srinivasan
2014-12-10 23:30 ` KY Srinivasan
2014-12-11 10:53 ` Sitsofe Wheeler
2014-12-11 10:53 ` Sitsofe Wheeler
2014-12-11 18:49 ` KY Srinivasan
2014-12-11 18:49 ` KY Srinivasan
2014-12-12 3:03 ` Martin K. Petersen [this message]
2014-12-12 3:03 ` Martin K. Petersen
2014-12-16 2:11 ` Long Li
2014-12-16 2:11 ` Long Li
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=yq1vblhbmcv.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=JBottomley@parallels.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@microsoft.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.