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 <dennis.dalessandro@intel.com> Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com> Signed-off-by: Jubin John <jubin.john@intel.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
This commit is contained in:
parent
849e3e9398
commit
e6d2e0176e
|
@ -1637,9 +1637,9 @@ bail:
|
||||||
spin_unlock_irqrestore(&qp->s_hlock, flags);
|
spin_unlock_irqrestore(&qp->s_hlock, flags);
|
||||||
if (nreq) {
|
if (nreq) {
|
||||||
if (call_send)
|
if (call_send)
|
||||||
rdi->driver_f.schedule_send_no_lock(qp);
|
|
||||||
else
|
|
||||||
rdi->driver_f.do_send(qp);
|
rdi->driver_f.do_send(qp);
|
||||||
|
else
|
||||||
|
rdi->driver_f.schedule_send_no_lock(qp);
|
||||||
}
|
}
|
||||||
return err;
|
return err;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue