From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] using nvmf target/initiator in spdk
Date: Tue, 02 Aug 2016 16:06:11 +0000 [thread overview]
Message-ID: <1470153970.2387.248.camel@intel.com> (raw)
In-Reply-To: 6e232ad7fe75285fb2724d128934d3d2@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
On Tue, 2016-08-02 at 15:52 +0530, Kirubakaran Kaliannan wrote:
>
>
> Hi,
>
> Do we have a document on, how to use the spdk to perform the following
>
> 1. List the devices that SPDK can see
You can run the identify or nvme_manage example to get a nice list of all of the devices that SPDK
can attach to. They are in examples/nvme.
> 2. Start nvmf target driver with nvme devices
We have this page: http://www.spdk.io/spdk/doc/nvmf_getting_started.html, which is accurate for our
last tagged release but has gone stale for the code on 'master'. We'll have an updated one shortly.
Right now it's fairly early stages, so you mostly have to just read the code. Our configuration file
is reasonably well documented too.
> 3. What nvmf initiator that we can use to connect this on the host machine (ubuntu)?
We test against the NVMe-oF initiator that will be added to the Linux kernel. It currently exists as
a set of patches against kernel 4.8. Here is an article from Mellanox explaining how to set up your
Linux kernel for NVMe-oF: https://community.mellanox.com/docs/DOC-2508. SPDK can run against
essentially any modern Linux kernel, so you only have to put kernel 4.8 on the initiator system.
>
>
> Thanks,
> -kiru
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-08-02 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 16:06 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-09 21:16 [SPDK] using nvmf target/initiator in spdk Verkamp, Daniel
2016-08-09 5:56 Kirubakaran Kaliannan
2016-08-07 4:34 Kirubakaran Kaliannan
2016-08-04 7:38 Kirubakaran Kaliannan
2016-08-04 1:46 Kirubakaran Kaliannan
2016-08-03 10:43 Minfei Huang
2016-08-02 10:22 Kirubakaran Kaliannan
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=1470153970.2387.248.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.