Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752673AbdGFWR4 (ORCPT ); Thu, 6 Jul 2017 18:17:56 -0400 Received: from verein.lst.de ([213.95.11.211]:33616 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752341AbdGFWRz (ORCPT ); Thu, 6 Jul 2017 18:17:55 -0400 Date: Fri, 7 Jul 2017 00:17:54 +0200 From: Christoph Hellwig To: David Wayne Fugate Cc: Keith Busch , Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] NVMe: Added another device ID with stripe quirk Message-ID: <20170706221754.GA10217@lst.de> References: <1499379151-32479-1-git-send-email-david.fugate@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1499379151-32479-1-git-send-email-david.fugate@intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 389 Lines: 7 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.