You can think of SPDK as a static library. Your program will link
against the library and then while your program runs, it will claim the
NVMe devices. When your program exits, it will release them. This is
what all of our examples are demonstrating.
Right now, SPDK only provides the NVMe driver, so you only have direct
block access to the device using our API in include/spdk/nvme.h. Since
it runs in user space, you cannot use any kernel facilities like lsblk
or even file systems to perform I/O. You can only write a program using
our API to do reads and writes from code.
On Fri, 2016-01-29 at 15:58 +0000, Sunny Raj wrote:
> Hi all,
> After binding SPDK with NVMe, how should I go about using the device
> itself? Once the NVMe is using SPDK, the kernel doesn't see it,
> meaning, `lsblk` won't show the device. I was successful in getting
> some meaningful numbers by running `spdk/examples/nvme/perf/perf`.
> What would be the next step? How do I go about actually using the
> device to perform I/O operations such as creating files?
> SPDK mailing list