netdev - RE: [PATCH net-next] bnx2x: Do Tx handling in a separate tasklet.

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 26 Oct 2009 07:42:27 -0700
From:	"Vladislav Zolotarov" <vladz@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	"Eilon Greenstein" <eilong@...adcom.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next] bnx2x: Do Tx handling in a separate
 tasklet.

The separation of Tx and Rx interrupt handling gives us the possibility to properly affinitize the Rx (heavy CPU consuming task) and Tx (low CPU consuming task) and to ensure that Tx work is done not long after the Tx interrupt without interference of Rx work thus letting the user benefit from Tx coalescing configuration in order to achieve the best performance in each specific scenario. This is most important in heavy load scenarios with mixed traffic (UDP + TCP for instance). If we didn't separate Tx and Rx interrupt handling Tx coalescing configuration was not worth much.

The mentioned above lead us to conclusion that it's more efficient not to use NAPI for freeing Tx buffers but to use a separate tasklet instead.

Best regards,
vlad

-----Original Message-----
From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org] On Behalf Of David Miller
Sent: Sunday, October 25, 2009 11:21 PM
To: Vladislav Zolotarov
Cc: Eilon Greenstein; netdev@...r.kernel.org
Subject: Re: [PATCH net-next] bnx2x: Do Tx handling in a separate tasklet.

From: "Vladislav Zolotarov" <vladz@...adcom.com>
Date: Sun, 25 Oct 2009 14:19:42 +0200

> This patch moves the 'Tx interrupt work' of each Tx queue from the hardIRQ
> context to the separate low-latency tasklet. Otherwise there is a possibility
> of a software lockup situation in a Tx softIRQ as it handles freeing all skb's
> 'freed' in (hard)IRQ context.
> 
> Signed-off-by: Vladislav Zolotarov <vladz@...adcom.com>
> Signed-off-by: Eilon Greenstein <eilong@...adcom.com>

Use NAPI, please...
--
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

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