[adding linux-nvme to Cc as the patch changes the nvme driver, despite
the subject line]
On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote:
On 02/25/2017 07:21 PM, Christoph Hellwig wrote:
On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote:
More implementations of
On Mon, Feb 27, 2017 at 08:35:06PM +0200, Sagi Grimberg wrote:
> > On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote:
> > > On 02/25/2017 07:21 PM, Christoph Hellwig wrote:
> > > > No way in hell. vs is vendor specific and we absolutely can't overload
> > > > it with any sort of mean
[adding linux-nvme to Cc as the patch changes the nvme driver, despite
the subject line]
On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote:
> On 02/25/2017 07:21 PM, Christoph Hellwig wrote:
> > On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote:
> > > More implementatio
On 02/25/2017 07:21 PM, Christoph Hellwig wrote:
On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote:
More implementations of OCSSDs are becoming available. Adding each using
pci ids are becoming a hassle. Instead, use a 16 byte string in the
vendor-specific area of the identificatio
On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote:
> More implementations of OCSSDs are becoming available. Adding each using
> pci ids are becoming a hassle. Instead, use a 16 byte string in the
> vendor-specific area of the identification command to identify an
> Open-Channel SSD.
>
More implementations of OCSSDs are becoming available. Adding each using
pci ids are becoming a hassle. Instead, use a 16 byte string in the
vendor-specific area of the identification command to identify an
Open-Channel SSD.
The large string should make the collision probability with other
vendor-
6 matches
Mail list logo
