| commit | 23f3bc0f2c1e26215b671499c07047c325d54d9c | |
| author | Michael S. Tsirkin <mst@mellanox.co.il> | |
| Thu, 18 May 2006 15:32:54 +0000 (18 18:32 +0300) | ||
| committer | Roland Dreier <rolandd@cisco.com> | |
| Thu, 18 May 2006 18:37:03 +0000 (18 11:37 -0700) | ||
| tree | a76e595b413de71d7f6fae1d959566447e1f6c5e | treesnapshot (tar.gz zip) |
| parent | 0cb4fe8d2658dc0bd1accfbb74ee288a9d6788f4 | commitdiff |
IB/mthca: Fix posting lists of 256 receive requests for Tavor
If we post a list of length 256 exactly, nreq in doorbell gets set to
256 which is wrong: it should be encoded by 0. This is because we
only zero it out on the next WR, which may not be there. The solution
is to ring the doorbell after posting a WQE, not before posting the
next one.
Signed-off-by: Michael S. Tsirkin <mst@mellanox.co.il>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
If we post a list of length 256 exactly, nreq in doorbell gets set to
256 which is wrong: it should be encoded by 0. This is because we
only zero it out on the next WR, which may not be there. The solution
is to ring the doorbell after posting a WQE, not before posting the
next one.
Signed-off-by: Michael S. Tsirkin <mst@mellanox.co.il>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
| drivers/infiniband/hw/mthca/mthca_qp.c | diffblobblamehistory |