From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] hotplug support and testing
Date: Tue, 28 Feb 2017 16:35:24 +0000 [thread overview]
Message-ID: <1488299722.9792.7.camel@intel.com> (raw)
In-Reply-To: 21E61B56-16F8-4016-B36A-FB6E5E2D0C74@ocient.com
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
On Mon, 2017-02-27 at 22:58 +0000, Will Del Genio wrote:
> Hello,
>
> I’m currently working on testing the hotplug support for local PCIe
> connected NVMe drives (P3700s and 3600s at the moment) on linux.
> (Linux sb1 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux)
>
> Right now spdk requires the setup script to be manually run which
> unbinds the nvme driver and binds the uio_pci_generic driver. Is
> there a way to have that happen automatically on hotplugging of an
> nvme device? From what I understand it could be done via script
> called by a udev rule.
You can change which devices the kernel assigns to which drivers by
writing to /sys/bus/pci/drivers/.../new_id and
/sys/bus/pci/drivers/.../remove_id. See
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-pci
If you change NVMe devices to automatically be bound to
uio_pci_generic, then SPDK will pick them up in the next
call to spdk_nvme_probe().
>
> Is that the right way to handle it? Are there any other plans for
> hotplug support moving forward I should be aware of?
>
> Thanks for the help,
> Will Del Genio
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]
next reply other threads:[~2017-02-28 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 16:35 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-28 0:52 [SPDK] hotplug support and testing Chang, Cunyin
2017-02-27 22:58 Will Del Genio
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=1488299722.9792.7.camel@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