rdma_reg_read()

rdma_reg_read()

[Steve Wise]

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

RE: rdma_reg_read()

[Hefty, 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?

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'? 
--
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

Re: rdma_reg_read()

[Steve Wise]

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

RE: rdma_reg_read()

[Hefty, Sean]

> 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.

Then I think that maps to the rdma_reg_write() call.
--
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