From: "Ye, Jinhe" <email@example.com>
To: Keith Busch <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>
Cc: "Zheng, Wu" <firstname.lastname@example.org>,
Subject: RE: [PATCH] nvme-pci: add another device ID with stripe quirk
Date: Wed, 17 Mar 2021 08:58:23 +0000 [thread overview]
Message-ID: <MN2PR11MB4221937A2D8E84C1BAF4D4239D6A9@MN2PR11MB4221.namprd11.prod.outlook.com> (raw)
Checked P5510 and it supports noiob field.
nvme id-ns /dev/nvme0n1 |grep noiob
noiob : 256
The purpose of the patch is for customers who are using old kernels. May I know from which kernel will support "stripe" quirk by noiob field checking? Thank you!
From: Keith Busch <email@example.com>
Sent: Wednesday, March 17, 2021 5:09 AM
To: Christoph Hellwig <firstname.lastname@example.org>
Cc: Zheng, Wu <email@example.com>; firstname.lastname@example.org; Ye, Jinhe <email@example.com>
Subject: Re: [PATCH] nvme-pci: add another device ID with stripe quirk
On Tue, Mar 16, 2021 at 07:30:42AM +0000, Christoph Hellwig wrote:
> On Mon, Mar 15, 2021 at 11:22:18PM -0400, Zheng Wu wrote:
> > From: Wu Zheng <firstname.lastname@example.org>
> > Adds the Intel controller of P5510 which has the "stripe" quirk.
> > Signed-off-by: Zheng Wu <email@example.com>
> > Signed-off-by: Ye Jinhe <firstname.lastname@example.org>
> I'm pretty sure we said we're not going add more of these years after
> there has been a standard way to communicate this performance
> preference using the noiob field.
P5510 was a Q4'20 release and NOIOB is 4 years older than that!
Jinhe, is it possible to reiterate to the development side how painful this non-standard behavior is to the nvme ecosystem? The spec compliant method is a simple and harmless f/w change that will make all your Linux customers better off.
Linux-nvme mailing list
next prev parent reply other threads:[~2021-03-17 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 3:22 [PATCH] nvme-pci: add another device ID with stripe quirk Zheng Wu
2021-03-16 7:30 ` Christoph Hellwig
2021-03-16 21:08 ` Keith Busch
2021-03-17 8:58 ` Ye, Jinhe [this message]
2021-03-17 14:16 ` Keith Busch
2021-03-16 16:12 Zheng Wu
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).