On 26/07/2013 20:15, Vu Pham wrote:
Hello Or/Sagi,
Just a minor
/**
+ * iser_create_frwr_pool - Creates pool of fast_reg descriptors
+ * for fast registration work requests.
+ * returns 0 on success, or errno code on failure
+ */
+int iser_create_frwr_pool(struct iser_conn *ib_conn, unsigned
On 7/28/2013 11:15 AM, Or Gerlitz wrote:
On 26/07/2013 20:15, Vu Pham wrote:
Hello Or/Sagi,
Just a minor
/**
+ * iser_create_frwr_pool - Creates pool of fast_reg descriptors
+ * for fast registration work requests.
+ * returns 0 on success, or errno code on failure
+ */
+int
On 07/24/13 18:28, Or Gerlitz wrote:
On 23/07/2013 17:47, Bart Van Assche wrote:
Still regarding page sizes: shouldn't ib_alloc_fast_reg_page_list()
and ib_alloc_fast_reg_mr() multiply the SG list length by PAGE_SIZE /
SIZE_4K to compensate for page size differences on architectures where
Hello Or/Sagi,
Just a minor
/**
+ * iser_create_frwr_pool - Creates pool of fast_reg descriptors
+ * for fast registration work requests.
+ * returns 0 on success, or errno code on failure
+ */
+int iser_create_frwr_pool(struct iser_conn *ib_conn, unsigned cmds_max)
+{
+ struct
On 23/07/2013 17:47, Bart Van Assche wrote:
Sorry but I had overlooked the bounce buffer patch. Regarding page
sizes: is an InfiniBand HCA required to support a page size of 512
bytes ? To me it seems like the smallest page size supported by e.g.
the ocrdma driver is 4KB. From
On 07/22/13 15:11, Sagi Grimberg wrote:
So just to clarify the flow:
. at connection establishment allocate pool of fastreg descriptors
. upon each IOP take a fastreg descriptor from the pool
. if it is not invalidated - invalidate it.
. register using FRWR.
. when cleanup_task is
On Tue, Jul 23, 2013 at 2:58 PM, Bart Van Assche bvanass...@acm.org wrote:
[...]
Hello Sagi and Or,
Thanks for the clarifications. I have one more question though. My
interpretation of section 10.6 Memory Management in the IB specification is
that memory registration maps a memory region
On 7/23/2013 2:58 PM, Bart Van Assche wrote:
On 07/22/13 15:11, Sagi Grimberg wrote:
So just to clarify the flow:
. at connection establishment allocate pool of fastreg descriptors
. upon each IOP take a fastreg descriptor from the pool
. if it is not invalidated - invalidate it.
.
On 07/23/13 16:21, Or Gerlitz wrote:
Bart, iSER's FMR and FRWR code works under the assumption that an SG
list is 4K aligned. For SGs which don't obey that assumption we're
using bounce buffer.
Note that the SG page size used by FMRs/FRWRs doesn't have to be 1:1
with the OS page size, so in
On 07/18/13 15:25, Or Gerlitz wrote:
+static int iser_fast_reg_mr(struct fast_reg_descriptor *desc,
+ struct iser_conn *ib_conn,
+ struct iser_regd_buf *regd_buf,
+ u32 offset, unsigned int data_size,
+
On 7/22/2013 2:46 PM, Bart Van Assche wrote:
On 07/18/13 15:25, Or Gerlitz wrote:
+static int iser_fast_reg_mr(struct fast_reg_descriptor *desc,
+struct iser_conn *ib_conn,
+struct iser_regd_buf *regd_buf,
+u32 offset, unsigned int data_size,
+
On Mon, Jul 22, 2013 at 2:46 PM, Bart Van Assche bvanass...@acm.org wrote:
[...]
What will happen if a new FRWR is submitted with an rkey that is still valid ?
The HW will fail this WR, we must invalidate the mapping before re-using the MR.
Or.
--
To unsubscribe from this list: send the line
From: Sagi Grimberg sa...@mellanox.com
Newer HCAs and Virtual functions may not support FMRs but rather a fast
registration model, which we call FRWR - Fast Registration Work Requests.
This model was introduced in 00f7ec36c RDMA/core: Add memory management
extensions support and works when the
13 matches
Mail list logo
