From: Christoph Hellwig <hch@lst.de>
To: David Wayne Fugate <david.fugate@intel.com>
Cc: Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NVMe: Added another device ID with stripe quirk
Date: Fri, 7 Jul 2017 00:17:54 +0200 [thread overview]
Message-ID: <20170706221754.GA10217@lst.de> (raw)
In-Reply-To: <1499379151-32479-1-git-send-email-david.fugate@intel.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] NVMe: Added another device ID with stripe quirk
Date: Fri, 7 Jul 2017 00:17:54 +0200 [thread overview]
Message-ID: <20170706221754.GA10217@lst.de> (raw)
In-Reply-To: <1499379151-32479-1-git-send-email-david.fugate@intel.com>
On Thu, Jul 06, 2017@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.
next parent reply other threads:[~2017-07-06 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1499379151-32479-1-git-send-email-david.fugate@intel.com>
2017-07-06 22:17 ` Christoph Hellwig [this message]
2017-07-06 22:17 ` [PATCH] NVMe: Added another device ID with stripe quirk Christoph Hellwig
2017-07-06 22:39 ` Keith Busch
2017-07-06 22:39 ` Keith Busch
2017-07-06 23:22 ` Christoph Hellwig
2017-07-06 23:22 ` Christoph Hellwig
2017-07-10 5:52 ` Sagi Grimberg
2017-07-10 5:52 ` Sagi Grimberg
2017-07-10 18:39 ` David Wayne Fugate
2017-07-12 10:30 ` Sagi Grimberg
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=20170706221754.GA10217@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=david.fugate@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.