From: David Miller <davem@davemloft.net>
To: romieu@fr.zoreil.com
Cc: netdev@vger.kernel.org, davej@redhat.com,
marc.c.dionne@gmail.com, tglx@linutronix.de, js@sig21.net,
realnc@gmail.com, hayeswang@realtek.com
Subject: Re: [PATCH] r8169: avoid NAPI scheduling delay.
Date: Sun, 10 Jun 2012 20:21:28 -0700 (PDT) [thread overview]
Message-ID: <20120610.202128.2099230010518549663.davem@davemloft.net> (raw)
In-Reply-To: <20120609205316.GA5915@electric-eye.fr.zoreil.com>
From: Francois Romieu <romieu@fr.zoreil.com>
Date: Sat, 9 Jun 2012 22:53:16 +0200
> While reworking the r8169 driver a few months ago to perform the
> smallest amount of work in the irq handler, I took care of avoiding
> any irq mask register operation in the slow work dedicated user
> context thread. The slow work thread scheduled an extra round of NAPI
> work which would ultimately set the irq mask register as required,
> thus keeping such irq mask operations in the NAPI handler.
> It would eventually race with the irq handler and delay NAPI execution
> for - assuming no further irq - a whole ksoftirqd period. Mildly a
> problem for rare link changes or corner case PCI events.
>
> The race was always lost after the last bh disabling lock had been
> removed from the work thread and people started wondering where those
> pesky "NOHZ: local_softirq_pending 08" messages came from.
>
> Actually the irq mask register _can_ be set up directly in the slow
> work thread.
>
> Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
> Reported-by: Dave Jones <davej@redhat.com>
> Tested-by: Marc Dionne <marc.c.dionne@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2012-06-11 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 20:53 [PATCH] r8169: avoid NAPI scheduling delay Francois Romieu
2012-06-11 3:21 ` David Miller [this message]
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=20120610.202128.2099230010518549663.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@redhat.com \
--cc=hayeswang@realtek.com \
--cc=js@sig21.net \
--cc=marc.c.dionne@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=realnc@gmail.com \
--cc=romieu@fr.zoreil.com \
--cc=tglx@linutronix.de \
/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