From: asb@cin.ufpe.br (Angelo Brito)
Subject: Unable to find /dev/nvme0
Date: Fri, 12 Sep 2014 13:53:42 -0300 [thread overview]
Message-ID: <CAMjVwgQOC0hEOioLtyjnbJjaOuui_njijg1dbDEgehphW8G0CQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1409120835210.4696@AMR>
Hi Keith.
I am already doing user space programs that makes use of the driver's uapi.
Wang asked about an API. I tried to explain that he can use the uapi
and use UNIX commands.
Sorry for the confused reply.
Regards,
Angelo Silva Brito.
Graduate in Engenharia da Computa??o - UFPE
http://about.me/angelobrito
_________________________________________________
On Fri, Sep 12, 2014@11:56 AM, Keith Busch <keith.busch@intel.com> wrote:
>
> On Fri, 12 Sep 2014, Angelo Brito wrote:
>>
>> I don't know any NVMe API. If there is an API for this driver the guys
>> from the nvme list can comment about it.
>> I have been working with NVMe driver, to do so I included the nvme.h
>> from kernel headers from usr/src/kernel/linux/include folders and
>> calling drivers functions directly.
>>
>> On Fri, Sep 12, 2014@4:39 AM, Haomai Wang <haomaiwang@gmail.com> wrote:
>>>
>>> Another question: where can I found the NVME API example program?
>>> nvme-user repo seemed too poor.
>
>
> I'm having a hard time parsing this conversation into something that
> makes sense. Are you asking for an example user space program that makes
> use of the linux nvme driver's uapi? I don't think you'll find a simpler
> example than those in the nvme user repo. Or perhaps you can suggest
> what you think it's lacking?
next prev parent reply other threads:[~2014-09-12 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 4:23 Unable to find /dev/nvme0 Haomai Wang
2014-09-12 7:12 ` Angelo Brito
2014-09-12 7:31 ` Haomai Wang
[not found] ` <CACJqLyacaeC43adhNb1VLbEa+hrwZ=_q+VXER1DEpBNDwbyA0Q@mail.gmail.com>
2014-09-12 14:19 ` Angelo Brito
2014-09-12 14:56 ` Keith Busch
2014-09-12 16:53 ` Angelo Brito [this message]
2014-09-13 8:54 ` Haomai Wang
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=CAMjVwgQOC0hEOioLtyjnbJjaOuui_njijg1dbDEgehphW8G0CQ@mail.gmail.com \
--to=asb@cin.ufpe.br \
/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.