IB/ipoib: Use debug prints instead of warnings in RNR WC status
authorFeras Daoud <ferasda@mellanox.com>
Wed, 28 Dec 2016 12:47:26 +0000 (14:47 +0200)
committerDoug Ledford <dledford@redhat.com>
Thu, 12 Jan 2017 19:01:05 +0000 (14:01 -0500)
If a receive request has not been posted to the work queue, the incoming
message is rejected and the peer will receive a receiver-not-ready (RNR)
error. In IPoIB, IB_WC_RNR_RETRY_EXC_ERR error is part of the life cycle
therefore ipoib_cm_handle_tx_wc function will print to debug instead
of warnings.

Signed-off-by: Feras Daoud <ferasda@mellanox.com>
Signed-off-by: Erez Shitrit <erezsh@mellanox.com>
Signed-off-by: Leon Romanovsky <leon@kernel.org>
Reviewed-by: Yuval Shaia <yuval.shaia@oracle.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
drivers/infiniband/ulp/ipoib/ipoib_cm.c

index a720d2ddddc159884a2c62a120563c84cdad66d7..c433e72994f5ee1b61a65740e61b678ade1960ce 100644 (file)
@@ -820,9 +820,12 @@ void ipoib_cm_handle_tx_wc(struct net_device *dev, struct ib_wc *wc)
            wc->status != IB_WC_WR_FLUSH_ERR) {
                struct ipoib_neigh *neigh;
 
-               ipoib_dbg(priv, "failed cm send event "
-                          "(status=%d, wrid=%d vend_err %x)\n",
-                          wc->status, wr_id, wc->vendor_err);
+               if (wc->status != IB_WC_RNR_RETRY_EXC_ERR)
+                       ipoib_warn(priv, "failed cm send event (status=%d, wrid=%d vend_err %x)\n",
+                                  wc->status, wr_id, wc->vendor_err);
+               else
+                       ipoib_dbg(priv, "failed cm send event (status=%d, wrid=%d vend_err %x)\n",
+                                 wc->status, wr_id, wc->vendor_err);
 
                spin_lock_irqsave(&priv->lock, flags);
                neigh = tx->neigh;