All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jonathan Woithe <jwoithe@atrad.com.au>
Cc: "Francois Romieu" <romieu@fr.zoreil.com>,
	"Holger Hoffstätte" <holger@applied-asynchrony.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: Thu, 18 Oct 2018 08:03:32 +0200	[thread overview]
Message-ID: <8beda4fa-5d04-49e6-eb3e-5656897a301f@gmail.com> (raw)
In-Reply-To: <20181018055835.GE2487@marvin.atrad.com.au>

On 18.10.2018 07:58, Jonathan Woithe wrote:
> On Thu, Oct 18, 2018 at 01:30:51AM +0200, Francois Romieu wrote:
>> Holger Hoffstätte <holger@applied-asynchrony.com> :
>> [...]
>>> I continued to use the BQL patch in my private tree after it was reverted
>>> and also had occasional timeouts, but *only* after I started playing
>>> with ethtool to change offload settings. Without offloads or the BQL patch
>>> everything has been rock-solid since then.
>>> The other weird problem was that timeouts would occur on an otherwise
>>> *completely idle* system. Since that occasionally borked my NFS server
>>> over night I ultimately removed BQL as well. Rock-solid since then.
>>
>> The bug will induce delayed rx processing when a spike of "load" is
>> followed by an idle period.
> 
> If this is the case, I wonder whether this bug might also be the cause of
> the long reception delays we've observed at times when a period of high
> network load is followed by almost nothing[1].  That thread[2] details the
> investigations subsequently done.  A git bisect showed that commit
> da78dbff2e05630921c551dbbc70a4b7981a8fff was the origin of the misbehaviour
> we were observing.
> 
> We still see the problem when we test with recent kernels.  It would be
> great if the underlying problem has now been identified.
> 
> I can possibly scrape some hardware together to test any proposed fix under
> our workload if there was interest.
> 
Proposed fix is here:
https://patchwork.ozlabs.org/patch/985014/
Would be good if you could test it. Thanks!

Heiner

> Regards
>   jonathan
> 
> [1] https://marc.info/?l=linux-netdev&m=136281333207734&w=2
> [2] https://marc.info/?t=136281339500002&r=1&w=2
> 

  reply	other threads:[~2018-10-18 14:02 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
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 [this message]
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=8beda4fa-5d04-49e6-eb3e-5656897a301f@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=davem@davemloft.net \
    --cc=holger@applied-asynchrony.com \
    --cc=jwoithe@atrad.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=romieu@fr.zoreil.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.