From: Daniel Verkamp <daniel.verkamp at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Is there any plan to add "quirk" mechanism to SPDK?
Date: Mon, 12 Sep 2016 09:20:47 -0700 [thread overview]
Message-ID: <32ad3c56-0af5-51ae-af4b-7bafa1bffdca@intel.com> (raw)
In-Reply-To: 1473444217.2810.17.camel@intel.com
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On 09/09/2016 11:03 AM, Walker, Benjamin wrote:
> Currently we have no mechanism for adding device-specific quirks to the
> SPDK NVMe driver. We'd certainly consider adding quirks in the same
> fashion as the Linux kernel driver though, and would welcome patches
> that improved the applicability of SPDK to a wider range of (potentially
> out of spec) devices. I'm sure over time the team at Intel working on
> SPDK will add this, but it is not on our immediate roadmap, so patches
> from the community would be the best way to get this going.
>
> Thanks,
> Ben
The SPDK NVMe driver does have a quirk system that is currently used
only for Intel-specific quirks (see lib/nvme/nvme_intel.c); however, the
structure used just matches against a PCI device ID in a generic way, so
we should be able to extend this for use with other devices.
I think the ideal first patch to add such a quirk would be to rename the
nvme_intel file and structures to be generic. Then we could add new
quirk flags to describe whatever non-spec-compliant behavior is required
to make these devices work.
Thanks,
-- Daniel
next reply other threads:[~2016-09-12 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 16:20 Daniel Verkamp [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-28 16:33 [SPDK] Is there any plan to add "quirk" mechanism to SPDK? Walker, Benjamin
2016-09-28 2:16 Wang Weber
2016-09-09 18:03 Walker, Benjamin
2016-09-08 6:25 Wang Weber
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=32ad3c56-0af5-51ae-af4b-7bafa1bffdca@intel.com \
--to=spdk@lists.01.org \
/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