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: Using XRC between kernel and user space.
Date: Fri, 5 Apr 2013 08:45:48 +0300 [thread overview]
Message-ID: <515E650C.60004@mellanox.com> (raw)
In-Reply-To: <515DBC10.1080009-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On 4/4/2013 8:44 PM, Shlomo Pongratz wrote:
> Hi,
>
> I wonder how a kernel "program" and a user space one can communicate
> using XRC.
> A example for such an application is iSER kernel initiator connected
> to tgtd target that runs in user space.
> The XRC domain in the kernel is created with "struct ib_xrcd
> *ib_alloc_xrcd(struct ib_device *device)" while in the user space it
> is created with "static inline struct ibv_xrcd * ibv_open_xrcd(struct
> ibv_context *context, struct ibv_xrcd_init_attr *xrcd_init_attr)".
> When looking in "xrc_pingpong.c" example we can see that the attribute
> has some file descriptor of some file ("/tmp/xrc_domain").
> So how a kernel "program" on one machine can communicate with a user
> space program on another one?
> The XRC annex (page 9) sates that all QP should belong to the same XRC
> domain.
>
> S.P.
>
Sorry, I misinterpreted the annex.
I thank Roland for clarifying this to me.
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
prev parent reply other threads:[~2013-04-05 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:44 Using XRC between kernel and user space Shlomo Pongratz
[not found] ` <515DBC10.1080009-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-04-05 5:45 ` Shlomo Pongratz [this message]
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=515E650C.60004@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