tree 2fdaf36325f9cc31e8f908b57c6ebd1bc3bd00c5
parent 576d7e5e0fd208d5f071f6eddecc85467e95dcd5
author Barret Rhoden <brho@cs.berkeley.edu> 1425078311 -0500
committer Barret Rhoden <brho@cs.berkeley.edu> 1425315551 -0500

BNX2X: Transmit synchronization

The transmit function is called serially, per txdata, meaning there is only
ever one caller of it.  Instead of a netif lock, we use the poker, which
guarantees mutual exclusion (per poke_tracker).

The transmitter stops when the device is full.  Concurrently, the tx_int
could have freed up space in the tx ring.  When tx_int calls poke, poke
will make sure the transmit function runs at least once after poke is
called.  This ensures we don't stall on transmits.

If you're concerned about the network stack calling transmit over and
over while the TX ring is full, we can optimize slightly.  See the notes
above __bnx2x_tx_queue() for details.  In short, poke() is powerful, but
it won't solve all of your problems.