From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: simplify stripe quirk
Date: Fri, 16 Dec 2016 10:48:01 -0500 [thread overview]
Message-ID: <20161216154800.GB8888@localhost.localdomain> (raw)
In-Reply-To: <20161216080753.GB22912@infradead.org>
On Fri, Dec 16, 2016@12:07:53AM -0800, Christoph Hellwig wrote:
> So an OEM can take the Intel Cards, and stuff their own values into the
> vendor specific fields? This sounds bad as you can't rely on the
> existing quirks in any old Linux version (plus FreeBSD or spdk for that
> matter any more).
Yes, these are the same concerns I've raised, and a reason we're in the
process of standardizing the feature.
It's fortunately not common for an OEM to break the decoding assumptions
we were promised, but the problem exists. I think this patch is the best
I can do for these devices.
next prev parent reply other threads:[~2016-12-16 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 0:10 [PATCH] nvme: simplify stripe quirk Keith Busch
2016-12-15 8:32 ` Christoph Hellwig
2016-12-15 15:59 ` Keith Busch
2016-12-16 8:07 ` Christoph Hellwig
2016-12-16 15:48 ` Keith Busch [this message]
2016-12-17 7:13 ` Christoph Hellwig
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=20161216154800.GB8888@localhost.localdomain \
--to=keith.busch@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