[ofw] RDMA - send for multiple packets (can we use same key andvaddr + offset)

[Fab Tillier]

Another thing to keep in mind is the byte order.  The send_wr.remote_ops.vaddr is a network order value since it gets put on the wire by the hardware in the RDMA header.

-Fab

From: ofw-bounces at lists.openfabrics.org [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Sean Hefty
Sent: Wednesday, May 14, 2008 9:05 AM
To: 'rakesh thakur'; ofw at lists.openfabrics.org
Cc: tejendra.joshi at gmail.com
Subject: RE: [ofw] RDMA - send for multiple packets (can we use same key andvaddr + offset)

In principal this should work.  What did you set for your transfer size?

Is rdma_vaddr a uint64 or void*?  (I'm not sure that adding to a void * is standardized.)


I am able to successfully do a RDMA_WRITE operation with the given key and given vaddr for the first packet
send_wr.remote_ops.rkey = rdma_key; // #RDMA#
send_wr.remote_ops.vaddr = rdma_vaddr; // #RDMA#

But I am not able to transfer the second packet by changing the rdma_vaddr
send_wr.remote_ops.rkey = rdma_key; // #RDMA#
send_wr.remote_ops.vaddr = rdma_vaddr + pkt_num*pkt_size; // #RDMA to the next memory location in the same registered buffer

I am not sure whether it is legal to give a different virtual address(vaddr + offset) associated rdma_key with vaddr for RDMA_WRITE operation?
OR
Do i have to register all buffers individually and obtain different key associated with it?
OR
Is there a way out to do RDMA_WRITE at different offsets of the memory(registered)  using associated (only) one key?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20080514/70c56714/attachment.html>