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: <CAH=tA9E2MvxvKg=YLYBNppMsJVpn-xHmua2rDZFSzrrMy7rPHw@mail.gmail.com>
Date:	Mon, 22 Jun 2015 22:04:47 +0300
From:	Nicolae Rosia <nicolae.rosia@...il.com>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	Florian Fainelli <f.fainelli@...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

On Sat, Jun 20, 2015 at 7:43 PM, Francois Romieu <romieu@...zoreil.com> wrote:
> 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 ?
>
I can help with testing!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in