From: David Miller <davem@davemloft.net>
To: bpoirier@suse.com
Cc: jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] i40e: Invoke softirqs after napi_reschedule
Date: Fri, 13 Jan 2017 20:27:00 -0500 (EST) [thread overview]
Message-ID: <20170113.202700.720848716249365172.davem@davemloft.net> (raw)
In-Reply-To: <20170113010414.22708-1-bpoirier@suse.com>
From: Benjamin Poirier <bpoirier@suse.com>
Date: Thu, 12 Jan 2017 17:04:14 -0800
> The following message is logged from time to time when using i40e:
> NOHZ: local_softirq_pending 08
>
> i40e may schedule napi from a workqueue. Afterwards, softirqs are not run
> in a deterministic time frame. The problem is the same as what was
> described in commit ec13ee80145c ("virtio_net: invoke softirqs after
> __napi_schedule") and this patch applies the same fix to i40e.
>
> Signed-off-by: Benjamin Poirier <bpoirier@suse.com>
I hope to see this from one of Jeff's pull requests to me in the
near future.
prev parent reply other threads:[~2017-01-14 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 1:04 [PATCH] i40e: Invoke softirqs after napi_reschedule Benjamin Poirier
2017-01-13 1:15 ` Eric Dumazet
2017-01-13 1:51 ` Benjamin Poirier
2017-01-14 1:27 ` 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=20170113.202700.720848716249365172.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bpoirier@suse.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.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).