[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50004376.7060703@intel.com>
Date: Fri, 13 Jul 2012 08:49:10 -0700
From: Alexander Duyck <alexander.h.duyck@...el.com>
To: Eric Dumazet <eric.dumazet@...il.com>
CC: netdev@...r.kernel.org, davem@...emloft.net,
jeffrey.t.kirsher@...el.com, edumazet@...gle.com,
bhutchings@...arflare.com, therbert@...gle.com,
alexander.duyck@...il.com
Subject: Re: [RFC PATCH 1/2] net: Add new network device function to allow
for MMIO batching
On 07/13/2012 12:19 AM, Eric Dumazet wrote:
> On Wed, 2012-07-11 at 17:26 -0700, Alexander Duyck wrote:
>
>> +static inline void netdev_complete_xmit(struct netdev_queue *txq)
>> +{
>> + struct net_device *dev = txq->dev;
>> + const struct net_device_ops *ops = dev->netdev_ops;
>> +
>> + if (txq->dispatch_pending < txq->dispatch_limit) {
>> + if (netif_tx_queue_delayed(txq)) {
>> + txq->dispatch_pending++;
>> + return;
>> + }
>> +
>> + /* start of delayed write sequence */
>> + netif_tx_delay_queue(txq);
> I dont understand this part. Isnt a return missing here ?
>
>> + }
>> +
>> + txq->dispatch_pending = 0;
>> +
>> + ops->ndo_complete_xmit(dev, txq - &dev->_tx[0]);
>> +}
>> +
>
There is intentionally no return there. The idea is that the first
packet always gets through. It is what is going to later force the
interrupt that will force the final flush if it is needed. That is one
of the ways I am helping to reduce the latency of things such as TSO
which will only be using one or two frames per interrupt anyway.
Thanks,
Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists