asgardius/android_kernel_motorola_sm6225
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

cxgb4vf: Remove obsolete comment about the lack of a TX Timer Callback

Browse source 
Remove obsolete comment about the lack of a TX Timer Callback -- which
we now _do_ have ...

Signed-off-by: Casey Leedom <leedom@chelsio.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Casey Leedom 2010-06-29 12:53:39 +00:00 committed by David S. Miller
parent d6bebca92c
commit 64bb336c8f
1 changed files with 1 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
drivers/net/cxgb4vf/sge.c
View file

@ -1301,18 +1301,7 @@ int t4vf_eth_xmit(struct sk_buff *skb, struct net_device *dev)
* wait for acks to really free up the data the extra memory
* is even less. On the positive side we run the destructors
* on the sending CPU rather than on a potentially different
* completing CPU, usually a good thing. We also run them
* without holding our TX queue lock, unlike what
* reclaim_completed_tx() would otherwise do.
*
* XXX Actually the above is somewhat incorrect since we don't
* XXX yet have a periodic timer which reclaims TX Descriptors.
* XXX What's our plan for this?
* XXX
* XXX Also, we don't currently have a TX Queue lock but
* XXX that may be the result of not having any current
* XXX asynchronous path for reclaiming completed TX
* XXX Descriptors ...
* completing CPU, usually a good thing.
*
* Run the destructor before telling the DMA engine about the
* packet to make sure it doesn't complete and get freed