From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Troy Leedberg <troy-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>,
Felix Marti <felix-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: rdma_reg_read()
Date: Thu, 07 Nov 2013 18:17:29 -0600 [thread overview]
Message-ID: <527C2D99.9050407@opengridcomputing.com> (raw)
Hey Sean:
static inline struct ibv_mr *
rdma_reg_read(struct rdma_cm_id *id, void *addr, size_t length)
{
return ibv_reg_mr(id->pd, addr, length, IBV_ACCESS_LOCAL_WRITE |
IBV_ACCESS_REMOTE_READ);
}
Should this be used for the registering sink memory of an rdma read? If
so, it won't work for iWARP, which requires REMOTE_WRITE for the sink.
Should this code look at the transport type and set REMOTE_WRITE for
iwarp transports?
Steve.
--
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 reply other threads:[~2013-11-08 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 0:17 Steve Wise [this message]
[not found] ` <527C2D99.9050407-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-11-08 0:21 ` rdma_reg_read() Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237388CF63E9-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-08 0:33 ` rdma_reg_read() Steve Wise
[not found] ` <527C316E.50805-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-11-08 1:04 ` rdma_reg_read() 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=527C2D99.9050407@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=felix-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=troy-ut6Up61K2wZBDgjK7y7TUQ@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;
as well as URLs for NNTP newsgroup(s).