From 574f3128c5b2d2ef095c587c967a55bda8499186 Mon Sep 17 00:00:00 2001 From: Andy Grover Date: Mon, 19 Jul 2010 17:15:57 -0700 Subject: [PATCH] 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 Signed-off-by: Chris Mason Signed-off-by: Bang Nguyen --- net/rds/ib_cm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/rds/ib_cm.c b/net/rds/ib_cm.c index bd0301ae05fb..96c4cc01fba5 100644 --- 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) -- 2.50.1