linux-kernel - Re: [PATCH] NVMe: Added another device ID with stripe quirk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170706221754.GA10217@lst.de>
Date:   Fri, 7 Jul 2017 00:17:54 +0200
From:   Christoph Hellwig <hch@....de>
To:     David Wayne Fugate <david.fugate@...el.com>
Cc:     Keith Busch <keith.busch@...el.com>, Jens Axboe <axboe@...com>,
        Christoph Hellwig <hch@....de>,
        Sagi Grimberg <sagi@...mberg.me>,
        linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NVMe: Added another device ID with stripe quirk

On Thu, Jul 06, 2017 at 04:12:31PM -0600, David Wayne Fugate wrote:
> Adds a fourth Intel controller which has the "stripe" quirk.

NVMe has stadardized a way to communicate this information through
the Namespace Optimal IO Boundary (NOIOB) field in the Identify
Namespace structure, and Keith and Amber at Intel helped to define
this, so please actually implement it in your controllers.