linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: "Ye, Jinhe" <jinhe.ye@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"Zheng, Wu" <wu.zheng@intel.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-pci: add another device ID with stripe quirk
Date: Wed, 17 Mar 2021 23:16:21 +0900	[thread overview]
Message-ID: <20210317141621.GB26641@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <MN2PR11MB4221937A2D8E84C1BAF4D4239D6A9@MN2PR11MB4221.namprd11.prod.outlook.com>

On Wed, Mar 17, 2021 at 08:58:23AM +0000, Ye, Jinhe wrote:
> Checked P5510 and it supports noiob field. 
> nvme id-ns /dev/nvme0n1 |grep noiob
> noiob   : 256

Awesome! So you don't need the quirk. :)
 
> 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!

Linux initially supported noiob since v4.13, which was released 9/2017.
If you need to go older than that, I think backporting noiob support
is a better option adding more quirks.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-03-17 14:16 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
2021-03-17 14:16       ` Keith Busch [this message]
2021-03-16 16:12 Zheng Wu

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=20210317141621.GB26641@redsun51.ssa.fujisawa.hgst.com \
    --to=kbusch@kernel.org \
    --cc=hch@infradead.org \
    --cc=jinhe.ye@intel.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=wu.zheng@intel.com \
    /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 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).