Trond Myklebust wrote
All I should need to know is that I can advertise either dma handles or kernel
VAs
Maybe its obvious to some people here, but may I ask why there's a need
to post either dma address or kernel virtual address? is it application
need? hardware (e.g IB vs iWARP vs vendor
Or Gerlitz wrote:
Trond Myklebust wrote
All I should need to know is that I can advertise either dma handles
or kernel VAs
Maybe its obvious to some people here, but may I ask why there's a
need to post either dma address or kernel virtual address? is it
application need? hardware (e.g IB
Steve Wise wrote:
The NFSRDMA transport uses Fast Register Memory Regions. In this
particular section of code, the NFSRDMA client is building a fastreg
work request to bind a page list to a fastreg mr. You can read about
this in the IBTA spec on memory management extensions, or in the RDMA
Trond Myklebust wrote (earlier in this thread):
All I should need to know is that I can advertise either dma handles or
kernel VAs, and know that I can choose between two functions, say,
ib_send_wr_fastreg_dma_init() and ib_send_wr_fastreg_kva_init() to
initialise the ib_send_wr
Steve Wise wrote:
Trond Myklebust wrote (earlier in this thread):
All I should need to know is that I can advertise either dma handles or
kernel VAs, and know that I can choose between two functions, say,
ib_send_wr_fastreg_dma_init() and ib_send_wr_fastreg_kva_init() to
initialise the
Trond Myklebust wrote:
On Mon, 2009-05-11 at 21:14 -0400, Tom Talpey wrote:
At 08:44 PM 5/11/2009, Trond Myklebust wrote:
On Mon, 2009-05-11 at 19:13 -0500, Steve Wise wrote:
Trond Myklebust wrote:
On Mon, 2009-05-11 at 17:25 -0500, Steve Wise wrote:
