From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Vasiliy Tolstov <v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: dedicated list for rdma userspace programming
Date: Mon, 24 Apr 2017 13:42:59 +0300 [thread overview]
Message-ID: <20170424104259.GH14088@mtr-leonro.local> (raw)
In-Reply-To: <CACaajQu1jvvCYJk82_oGOGH7jbjXzbkw_YoggqvW7TZhXj4VBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Mon, Apr 24, 2017 at 12:58:53PM +0300, Vasiliy Tolstov wrote:
> Hi! Does this mailing list suitable for questions about rdma userspace
> programming or i need to find another list?
This is the right list.
>
> My question is - how userspace libraries communicate with kernel
> devices which provided by kernel infiniband drivers? This is character
> devices and userspace libraries read/write to it or userspace library
> do some ioctls?
There are number of char devices exported by infiniband subsystem
(/dev/infiniband/*) and the communication is performed with read/write
interfaces to uverbs file [1].
Right now, we are in process of migration from these interfaces to ioctl
based, see Matan's latest RFC [2].
[1] https://github.com/linux-rdma/rdma-core/blob/master/Documentation/libibverbs.md
[2] http://marc.info/?l=linux-rdma&m=149261526916544&w=2
>
> Where i can find info about it?
>
> --
> Vasiliy Tolstov,
> e-mail: v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-24 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 9:58 dedicated list for rdma userspace programming Vasiliy Tolstov
[not found] ` <CACaajQu1jvvCYJk82_oGOGH7jbjXzbkw_YoggqvW7TZhXj4VBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-24 10:42 ` Leon Romanovsky [this message]
[not found] ` <20170424104259.GH14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-24 11:07 ` Vasiliy Tolstov
[not found] ` <CACaajQu9y2HawOjeuwjYSHeFmYfhWreQORB5_61nPiEspoQ2JA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-24 11:47 ` Leon Romanovsky
[not found] ` <20170424114733.GI14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-24 11:58 ` Vasiliy Tolstov
[not found] ` <CACaajQs=04be-QDFgqjXj4u=qp4wC6KFU8y5g=kR7vkV0QkbdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-24 12:34 ` Leon Romanovsky
[not found] ` <20170424123413.GJ14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-24 12:45 ` Vasiliy Tolstov
[not found] ` <CACaajQueUDeiqb0jyPPT-OFL=sgEn=apffC2SpLFZR2pbi04fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-24 18:13 ` Leon Romanovsky
[not found] ` <20170424181351.GM14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-24 18:26 ` Vasiliy Tolstov
[not found] ` <CACaajQvf4fioVGoYqJexhOAbNFJPK0aYGbFW+52z3NFU9RKQcA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-24 18:31 ` Jason Gunthorpe
[not found] ` <20170424183137.GA27506-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-04-24 19:49 ` Vasiliy Tolstov
[not found] ` <CACaajQt8WZrCWXN5-JGovCcknwV9TKiy5gntzNmTjpmdxf6PJg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-24 20:10 ` Jason Gunthorpe
[not found] ` <20170424201033.GA28656-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-04-25 11:29 ` Vasiliy Tolstov
[not found] ` <CACaajQsMdNt++M=DStZ+27km04xNRRxpbcrSGS9av_qtUgPJHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-25 17:13 ` Hefty, Sean
2017-04-25 17:39 ` Jason Gunthorpe
[not found] ` <20170425173912.GA6242-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-04-25 20:41 ` Vasiliy Tolstov
2017-04-25 17:56 ` Leon Romanovsky
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=20170424104259.GH14088@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.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