All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Using SPDK to create files
Date: Fri, 29 Jan 2016 16:47:07 +0000	[thread overview]
Message-ID: <1454086027.61425.94.camel@intel.com> (raw)
In-Reply-To: CAGJRfpjoOWOZrgf-EeFg8KskAF71BKEHrbxdY454s+UK_nVqoQ@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hi Sunny,

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.

Thanks,
Ben

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?
> 
> Thanks,
> Sunny
> -- 
> Sunny
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

             reply	other threads:[~2016-01-29 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 16:47 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-29 15:58 [SPDK] Using SPDK to create files Sunny Raj

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=1454086027.61425.94.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.