On Mon, Apr 24, 2017 at 03:45:26PM +0300, Vasiliy Tolstov wrote: > 2017-04-24 15:34 GMT+03:00 Leon Romanovsky <leon@xxxxxxxxxx>: > >> >> And how much work needs to be done to get this work upstream? (1 > >> >> month, 6 months, years...) ? > >> > > >> > At least one kernel cycle, and after transition read/write will be > >> > obsolete and will be dropped. > >> > > >> > >> So 4.12-4.13 ? > > > > 4.12 is almost closed. We are in rc8 now and merge window will be next > > week, so it will be 4.13-4.14 (optimistic). > > > > Fine. So older interfaces will be deprecated and removed in next few > cycles. I think i can now create something that used old api and do > transition later (i'm use fedora) Yes, conversion should be possible, Matan and Jason invest a lot of time and effort to be sure that conversion will be as minimal as possible. > > >> > >> >> If i want to try working with uverbs without C librarary, where i can > >> >> find some info about format of messages reader and writed to uverbs > >> >> device? > >> > > >> > Did you see Documentation/infiniband/user_verbs.txt? > >> > >> > >> https://www.kernel.org/doc/Documentation/infiniband/user_verbs.txt as > >> i see this nothing says about format of data writed/readed... > >> > > > > See in include/uapi/rdma/ib_user_verbs.h, User fills struct from that > > file, and kernel performs copy_from_user to extract the data. That's > > all. > > Thanks! If i need to establish communication between two nodes and > send/recv data (and get notification that data can be readed) does > this file enough to do that? Yes, if performance is not critical to you. Otherwise, the best solution will be to take a look on implementation of data transfer (various post_send functions) in rdma-core library. > (i'm plan to try create plain go binding, now only for fun, create > generator for this C struct/enums to plain go types) > > > -- > Vasiliy Tolstov, > e-mail: v.tolstov@xxxxxxxxx
Attachment:
signature.asc
Description: PGP signature
