aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJubin John <[email protected]>2016-04-12 10:47:00 -0700
committerDoug Ledford <[email protected]>2016-04-28 12:00:39 -0400
commite6d2e0176e1f3c1e1534851b66c0b972f03ff069 (patch)
treee06b598385a9d2d070a4d1f2d6f02537be834909
parent849e3e9398608c26a7c54bf9fbf3288f7ced6bfb (diff)
IB/rdmavt: Fix send scheduling
call_send is used to determine whether to send immediately or schedule a send for later. The current logic in rdmavt is inverted and has a negative impact on the latency of the hfi1 and qib drivers. Fix this regression by correctly calling send immediately when call_send is set. Reviewed-by: Dennis Dalessandro <[email protected]> Reviewed-by: Mike Marciniszyn <[email protected]> Signed-off-by: Jubin John <[email protected]> Signed-off-by: Doug Ledford <[email protected]>
-rw-r--r--drivers/infiniband/sw/rdmavt/qp.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/infiniband/sw/rdmavt/qp.c b/drivers/infiniband/sw/rdmavt/qp.c
index bd82a6948dc8..a9e3bcc522c4 100644
--- a/drivers/infiniband/sw/rdmavt/qp.c
+++ b/drivers/infiniband/sw/rdmavt/qp.c
@@ -1637,9 +1637,9 @@ bail:
spin_unlock_irqrestore(&qp->s_hlock, flags);
if (nreq) {
if (call_send)
- rdi->driver_f.schedule_send_no_lock(qp);
- else
rdi->driver_f.do_send(qp);
+ else
+ rdi->driver_f.schedule_send_no_lock(qp);
}
return err;
}