netdev - Re: about latencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Apr 2009 16:01:06 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
cc:	"Eric Dumazet" <dada1@...mosbay.com>,
	"Christoph Lameter" <cl@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	"Linux Netdev List" <netdev@...r.kernel.org>,
	"Ben Hutchings" <bhutchings@...arflare.com>
Subject: Re: about latencies


On Thu, 2009-04-23 at 15:34 -0700, Brandeburg, Jesse wrote:
> On Thu, 23 Apr 2009, Eric Dumazet wrote:
> 
> > 3) changing bnx2_poll_work() to first call bnx2_rx_int(), then bnx2_tx_int() to consume tx.
> 
> at least all of the intel drivers that have a single vector (function) 
> handling interrupts, always call tx clean first so that any tx buffers are 
> free to be used immediately because the NAPI calls can generate tx traffic 
> (acks in the case of tcp and full routed packet transmits in the case of 
> forwarding)
> 

Are you talking about freeing the tx buffers in the tx ring to make room
for more tx packets?  As long as the tx ring is not previously full and
is now completely free and idle, it doesn't matter too much when we free
the tx buffers in the tx ring, does it?


--
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