- ctx-cq = ibv_create_cq(ctx-context, ctx-rx_depth, NULL, ctx-channel,
0);
+ ctx-cq = ibv_create_cq(ctx-context, ctx-tx_depth + ctx-rx_depth,
+ NULL, ctx-channel, 0);
I'm looking at a windows port of this test, but at least there, rx_depth is set
to rx_depth
On Thu, 2009-08-06 at 14:37 -0700, Sean Hefty wrote:
-ctx-cq = ibv_create_cq(ctx-context, ctx-rx_depth, NULL, ctx-channel,
0);
+ctx-cq = ibv_create_cq(ctx-context, ctx-tx_depth + ctx-rx_depth,
+NULL, ctx-channel, 0);
I'm looking at a windows port of this
Sure. Just above the call to ibv_create_cq(), ctx-rx_depth is set to
ctx-rx_depth = rx_depth + tx_depth
but the rest of the code does ibv_post_send() and ibv_post_recv()
based on ctx-tx_depth and ctx-rx_depth which means the CQ needs
to be ctx-tx_depth + ctx-rx_depth big.
If the tx_depth
On Thu, 2009-08-06 at 14:56 -0700, Sean Hefty wrote:
Sure. Just above the call to ibv_create_cq(), ctx-rx_depth is set to
ctx-rx_depth = rx_depth + tx_depth
but the rest of the code does ibv_post_send() and ibv_post_recv()
based on ctx-tx_depth and ctx-rx_depth which means the CQ needs
Remember that this fix only affects the bi-directional test.
Both client and sever are going to post ctx-rx_depth receives
and ctx-tx_depth sends and then check for completions.
It won't post more sends or receives until the completions are
seen.
Okay - I think I understand what's happening.
The
