From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Wise Subject: Re: rdma_reg_read() Date: Thu, 07 Nov 2013 18:33:50 -0600 Message-ID: <527C316E.50805@opengridcomputing.com> References: <527C2D99.9050407@opengridcomputing.com> <1828884A29C6694DAF28B7E6B8A8237388CF63E9@ORSMSX109.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237388CF63E9-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Hefty, Sean" Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Troy Leedberg , Felix Marti List-Id: linux-rdma@vger.kernel.org On 11/7/2013 6:21 PM, Hefty, Sean wrote: >> 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? > This is to register memory as the target of an RDMA read operation. I.e. the memory being read. Is that the same as your 'sink'? No, I would call that the 'source' of the read. Basically the mr to-which the read data is placed needs REMOTE_WRITE for iWARP. -- 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