IPoIB TX NAPI

It is very common in modern network devices to use NAPI in RX and TX, in the UD/TX flows IPoIB uses a polling mechanism (not as it does in the CM mode).

Except of the motivation to use the same mechanism for IPoIB as for netdevices, there are number of issues in current polling mechanism:
* SKBs that are kept longer than they should be and there are applications that warn about that (some firewalls for example).
* Statistics that are not updated to the real value. It blocks support for time synchronization protocols over the IPoIB protocol, like PTP and so on.
* The TX in CM mode already uses NAPI, there is no reason to keep two different ways for TX one for UD and one for the CM.

The patches are available in the git repository at:
git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git tags/rdma-next-2017-10-16-2

Thanks

Cc: Kamal Heib <kamalh-VPRAkNaXOzVWk0Htik3J/[email protected]>
---------------------------------------

Erez Shitrit (3):
IB/ipoib: Get rid of the tx_outstanding variable in all modes IB/ipoib: Use NAPI in UD/TX flows
IB/ipoib: Change number of TX wqe to 64

 drivers/infiniband/ulp/ipoib/ipoib.h       |  14 ++--
 drivers/infiniband/ulp/ipoib/ipoib_cm.c    |  46 ++++++-----
 drivers/infiniband/ulp/ipoib/ipoib_ib.c    | 127 ++++++++++++++++++-----------
 drivers/infiniband/ulp/ipoib/ipoib_main.c  |  25 ++++--
 drivers/infiniband/ulp/ipoib/ipoib_verbs.c |  17 ++--
 5 files changed, 143 insertions(+), 86 deletions(-)

--
2.14.2

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html