Use CQ_NEXT_COMP for recv completions

We want to get interrupts for incoming data with no delay.
Splitting the CQs lets us have different policies here and
for send, where we don't want an event for each send completion.

Signed-off-by: Andy Grover <andy.grover@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Signed-off-by: Bang Nguyen <bang.nguyen@oracle.com>

diff --git a/net/rds/ib_cm.c b/net/rds/ib_cm.c
index bd0301ae05fb8d8f233c5c0b197f09df8ff9313f..96c4cc01fba577b44b108121de526ebf2ee1708e 100644 (file)
--- a/net/rds/ib_cm.c
+++ b/net/rds/ib_cm.c
@@ -312,7 +312,7 @@ void rds_ib_tasklet_fn_recv(unsigned long data)
        memset(&ack_state, 0, sizeof(ack_state));
 
        poll_cq(ic, ic->i_rcq, ic->i_recv_wc, &ack_state);
-       ib_req_notify_cq(ic->i_rcq, IB_CQ_SOLICITED);
+       ib_req_notify_cq(ic->i_rcq, IB_CQ_NEXT_COMP);
        poll_cq(ic, ic->i_rcq, ic->i_recv_wc, &ack_state);
 
        if (ack_state.ack_next_valid)