netdev - Re: macb napi strange behavior

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]

Message-ID: <20150620164332.GA2505@electric-eye.fr.zoreil.com>
Date:	Sat, 20 Jun 2015 18:43:32 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Florian Fainelli <f.fainelli@...il.com>
Cc:	Nicolae Rosia <nicolae.rosia@...il.com>,
	Jaeden Amero <jaeden.amero@...com>,
	netdev <netdev@...r.kernel.org>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Cyrille Pitchen <cyrille.pitchen@...el.com>,
	Josh Cartwright <joshc@...com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: macb napi strange behavior

Florian Fainelli <f.fainelli@...il.com> :
[...]
> Typically, NAPI is used at the receive side of the Ethernet NIC/driver
> to lower the hard/soft interrupt context switch, although there is
> nothing that prevent you to implement a similar scheme for the
> transmit side. Usually, for transmit you will be submitting one packet
> for transmission and get a completion interrupt, so without interrupt
> coalescing (software or hardware) you can end-up with 1 interrupt per
> packet transmitted.

The wording is a bit shy: there is a long standing policy to move
everything to NAPI context (as well as go mostly lockless, etc.).

Any taker to move macb Tx processing to NAPI context or should I consider it ?

-- 
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in