From: Shlomo Pongratz <shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Different signatures to ibv_open_xrcd - branch issue?
Date: Tue, 26 Mar 2013 23:04:03 +0200 [thread overview]
Message-ID: <51520D43.2060006@mellanox.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A823736F36825D-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 3/26/2013 5:56 PM, Hefty, Sean wrote:
>> I understand that currently I can't do RDMA using XRC, is that the case?
>> How complicated are the required modifications needed to make librdmacm
>> complies to the libibverbs changes?
> The changes needed for the librdmacm to support XRC aren't huge. The complication is getting XRC merged with libibverbs.
I think I missed something here, can I use your branch xrc2 of
libibverbs for testing purpose, or there are still things to merge there?
And for librdmacm, I'm looking forward to try it with a real application
the moment you'll have a branch witch is compatible with libibverbs.
S.P.
--
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
next prev parent reply other threads:[~2013-03-26 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:51 Different signatures to ibv_open_xrcd - branch issue? Shlomo Pongratz
[not found] ` <51502C30.2000806-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-03-25 16:35 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736F367AB8-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-26 10:09 ` Shlomo Pongratz
[not found] ` <515173F2.4030506-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-03-26 15:56 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736F36825D-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-26 21:04 ` Shlomo Pongratz [this message]
[not found] ` <51520D43.2060006-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-03-26 21:09 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736F368566-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-04-04 8:22 ` Dominique Martinet
2013-04-04 14:39 ` Hefty, Sean
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=51520D43.2060006@mellanox.com \
--to=shlomop-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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