From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Florian Fainelli" <f.fainelli@gmail.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
David Miller <davem@davemloft.net>,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] r8169: fix NAPI handling under high load
Date: Tue, 16 Oct 2018 17:23:03 -0700 [thread overview]
Message-ID: <f22a01e4-a8d4-7358-00e8-89fd8401976f@gmail.com> (raw)
In-Reply-To: <92db72c9-1f8c-d6a5-bcf4-241fa4c5a310@gmail.com>
On 10/16/2018 04:08 PM, Florian Fainelli wrote:
> I had started doing that about a month ago in light of the ixbge
> ndo_poll_controller vs. napi problem, but have not had time to submit
> that series yet:
>
> https://github.com/ffainelli/linux/commits/napi-check
>
> feel free to piggy back on top of that series if you would like to
> address this.
But the root cause was different, you remember ?
We fixed the real issue with netpoll ability to stick all NIC IRQ onto one
victim CPU.
next prev parent reply other threads:[~2018-10-17 8:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 20:37 [PATCH net] r8169: fix NAPI handling under high load Heiner Kallweit
2018-10-16 21:17 ` Holger Hoffstätte
2018-10-16 23:03 ` Stephen Hemminger
2018-10-16 23:08 ` Florian Fainelli
2018-10-17 0:23 ` Eric Dumazet [this message]
2018-10-17 3:10 ` Florian Fainelli
2018-10-17 0:21 ` Eric Dumazet
2018-10-17 18:12 ` Heiner Kallweit
2018-10-17 18:48 ` Fwd: " Heiner Kallweit
2018-10-17 19:11 ` Holger Hoffstätte
2018-10-17 19:27 ` Heiner Kallweit
2018-10-17 20:07 ` Holger Hoffstätte
2018-10-20 9:55 ` Holger Hoffstätte
2018-10-17 23:30 ` Francois Romieu
2018-10-18 5:58 ` Jonathan Woithe
2018-10-18 6:03 ` Heiner Kallweit
2018-10-18 6:15 ` Jonathan Woithe
2018-10-18 11:52 ` Holger Hoffstätte
2018-10-19 7:29 ` Jonathan Woithe
2018-10-21 23:07 ` Jonathan Woithe
2018-10-16 22:17 ` Stephen Hemminger
2018-10-17 0:19 ` Eric Dumazet
2018-10-17 23:30 ` Francois Romieu
2018-10-18 5:21 ` David Miller
2018-10-18 5:58 ` Heiner Kallweit
2018-10-18 6:24 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f22a01e4-a8d4-7358-00e8-89fd8401976f@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=holger@applied-asynchrony.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).