be2net: Pad skb to meet min Tx pkt size in lancer

In Lancer, packets that are 32 bytes or less may cause a transmit stall.
The work-around is to pad such packets to a 36 byte length.

Signed-off-by: Kalesh AP <kalesh.purayil@emulex.com>
Signed-off-by: Somnath Kotur <somnath.kotur@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/drivers/net/ethernet/emulex/benet/be_main.c b/drivers/net/ethernet/emulex/benet/be_main.c
index d1580823c28637983219641fadd01905fe788d6d..26e222f8143371ea7bb2f99e7197c81a071fc772 100644 (file)
--- a/drivers/net/ethernet/emulex/benet/be_main.c
+++ b/drivers/net/ethernet/emulex/benet/be_main.c
@@ -848,6 +848,16 @@ static struct sk_buff *be_xmit_workarounds(struct be_adapter *adapter,
        unsigned int eth_hdr_len;
        struct iphdr *ip;
 
+       /* Lancer ASIC has a bug wherein packets that are 32 bytes or less
+        * may cause a transmit stall on that port. So the work-around is to
+        * pad such packets to a 36-byte length.
+        */
+       if (unlikely(lancer_chip(adapter) && skb->len <= 32)) {
+               if (skb_padto(skb, 36))
+                       goto tx_drop;
+               skb->len = 36;
+       }
+
        /* For padded packets, BE HW modifies tot_len field in IP header
         * incorrecly when VLAN tag is inserted by HW.
         */