From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
devel@linuxdriverproject.org, Christoph Hellwig <hch@lst.de>,
Sitsofe Wheeler <sitsofe@gmail.com>
Subject: Re: [PATCH 0/3] scsi: Add Hyper-V logical block provisioning quirks
Date: Sat, 11 Oct 2014 10:41:53 -0700 [thread overview]
Message-ID: <1413049313.2068.48.camel@jarvis.lan> (raw)
In-Reply-To: <20141011173902.GA1946@infradead.org>
On Sat, 2014-10-11 at 10:39 -0700, Christoph Hellwig wrote:
> On Fri, Oct 10, 2014 at 08:49:01AM +0100, Sitsofe Wheeler wrote:
> > Microsoft Hyper-V virtual disks currently only claim SPC-2 compliance
> > even though they implement post SPC-2 features (such as thin
> > provisioning) which means the Linux kernel does not go on to test for
> > those features even though they are advertised.
> >
> > A previous patch attempted to add a quirk to workaround this but the
> > quirk was only enabled after the features had been scanned for, wouldn't
> > work for "small" disks and would quirk on all Hyper-V SCSI devices
> > (e.g. passthrough disks).
> >
> > The new patches partially revert the previous effort, add the quirk in a
> > more traditional manner to only Hyper-V virtual disks and work on small
> > virtual disks.
>
> This seems like might want a quirk to simply "force" a SPC3 compliance
> level?
This was initially suggested, but rejected by Microsoft because of other
problems advertising SPC-3 compliance brings. Perhaps the hyper-v
emulator has matured sufficiently that it will now work OK?
James
WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sitsofe Wheeler <sitsofe@gmail.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org
Subject: Re: [PATCH 0/3] scsi: Add Hyper-V logical block provisioning quirks
Date: Sat, 11 Oct 2014 10:41:53 -0700 [thread overview]
Message-ID: <1413049313.2068.48.camel@jarvis.lan> (raw)
In-Reply-To: <20141011173902.GA1946@infradead.org>
On Sat, 2014-10-11 at 10:39 -0700, Christoph Hellwig wrote:
> On Fri, Oct 10, 2014 at 08:49:01AM +0100, Sitsofe Wheeler wrote:
> > Microsoft Hyper-V virtual disks currently only claim SPC-2 compliance
> > even though they implement post SPC-2 features (such as thin
> > provisioning) which means the Linux kernel does not go on to test for
> > those features even though they are advertised.
> >
> > A previous patch attempted to add a quirk to workaround this but the
> > quirk was only enabled after the features had been scanned for, wouldn't
> > work for "small" disks and would quirk on all Hyper-V SCSI devices
> > (e.g. passthrough disks).
> >
> > The new patches partially revert the previous effort, add the quirk in a
> > more traditional manner to only Hyper-V virtual disks and work on small
> > virtual disks.
>
> This seems like might want a quirk to simply "force" a SPC3 compliance
> level?
This was initially suggested, but rejected by Microsoft because of other
problems advertising SPC-3 compliance brings. Perhaps the hyper-v
emulator has matured sufficiently that it will now work OK?
James
next prev parent reply other threads:[~2014-10-11 17:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 7:49 [PATCH 0/3] scsi: Add Hyper-V logical block provisioning quirks Sitsofe Wheeler
2014-10-10 7:49 ` Sitsofe Wheeler
2014-10-10 7:51 ` [PATCH 1/3] Revert "Drivers: add blist flags" Sitsofe Wheeler
2014-10-10 7:51 ` Sitsofe Wheeler
2014-10-10 7:52 ` [PATCH 2/3] scsi: add try_rc16 blacklist flag Sitsofe Wheeler
2014-10-10 7:52 ` Sitsofe Wheeler
2014-10-15 1:08 ` Martin K. Petersen
2014-10-15 1:08 ` Martin K. Petersen
2014-10-15 2:07 ` KY Srinivasan
2014-10-21 4:21 ` Sitsofe Wheeler
2014-10-21 4:21 ` Sitsofe Wheeler
2014-10-23 1:46 ` Martin K. Petersen
2014-10-23 1:46 ` Martin K. Petersen
2014-10-10 7:55 ` [PATCH 3/3] scsi: Use try_rc16 and try_vpd_pages quirks on Hyper-V virtual disks Sitsofe Wheeler
2014-10-10 7:55 ` Sitsofe Wheeler
2014-10-11 17:39 ` [PATCH 0/3] scsi: Add Hyper-V logical block provisioning quirks Christoph Hellwig
2014-10-11 17:41 ` James Bottomley [this message]
2014-10-11 17:41 ` James Bottomley
2014-10-11 19:48 ` KY Srinivasan
2014-10-11 19:48 ` KY Srinivasan
2014-10-11 20:22 ` Jeff Leung
2014-10-11 20:22 ` Jeff Leung
2014-10-12 1:21 ` KY Srinivasan
2014-10-12 1:21 ` KY Srinivasan
2014-10-21 4:45 ` Sitsofe Wheeler
2014-10-21 4:45 ` Sitsofe Wheeler
2014-10-21 5:19 ` Jeff Leung
2014-10-21 5:19 ` Jeff Leung
2014-10-21 18:30 ` KY Srinivasan
2014-10-21 18:30 ` KY Srinivasan
2014-10-15 1:06 ` Martin K. Petersen
2014-10-15 1:06 ` Martin K. Petersen
2014-10-21 4:17 ` Sitsofe Wheeler
2014-10-21 4:17 ` Sitsofe Wheeler
2014-10-23 1:50 ` Martin K. Petersen
2014-10-23 1:50 ` Martin K. Petersen
2014-10-23 9:03 ` Sitsofe Wheeler
2014-10-23 9:03 ` Sitsofe Wheeler
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=1413049313.2068.48.camel@jarvis.lan \
--to=james.bottomley@hansenpartnership.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sitsofe@gmail.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.