From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>, davem@davemloft.net
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 12/15] i40evf: Drop i40evf_fire_sw_int as it is prone to races
Date: Thu, 4 Jan 2018 12:31:41 +0300 [thread overview]
Message-ID: <2d470a24-a79e-b0f4-3a91-5f2dd0be5da0@cogentembedded.com> (raw)
In-Reply-To: <20180103212222.17378-13-jeffrey.t.kirsher@intel.com>
Hello!
On 1/4/2018 12:22 AM, Jeff Kirsher wrote:
> From: Alexander Duyck <alexander.h.duyck@intel.com>
>
> Having the interrupts firing while we are polling causes extra overhead and
> isn't needed for most systems out there. If an interrupt is lost us
> experiencing a 2s latency spike before recovering is still not acceptable
> and masks the issue. We are better off just identifying systems that lose
> interrupts and instead enable workarounds for those systems.
>
> To that end I am dropping the code that was strobing the interrupts as
> there is a narrow window where having them enabled can actually cause
> race issues anyway where a few stray packets might get misses if the
> interrupt is re-enabled and fires before we call napi_complete.
>
> Also replace one line where we were using bit 31 instead of the define
> for the bit to represent masking the interrupt enable bit.
I'm not seeing this change...
> Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
> Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2018-01-04 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 21:22 [net-next 00/15][pull request] 40GbE Intel Wired LAN Driver Updates 2018-01-03 Jeff Kirsher
2018-01-03 21:22 ` [net-next 01/15] i40e: display priority_xon and priority_xoff stats Jeff Kirsher
2018-01-03 21:22 ` [net-next 02/15] i40evf: don't rely on netif_running() outside rtnl_lock() Jeff Kirsher
2018-01-03 21:22 ` [net-next 03/15] i40evf: use spinlock to protect (mac|vlan)_filter_list Jeff Kirsher
2018-01-03 21:22 ` [net-next 04/15] i40evf: release bit locks in reverse order Jeff Kirsher
2018-01-03 21:22 ` [net-next 05/15] i40evf: hold the critical task bit lock while opening Jeff Kirsher
2018-01-03 21:22 ` [net-next 06/15] i40e: update VFs of link state after GET_VF_RESOURCES Jeff Kirsher
2018-01-03 21:22 ` [net-next 07/15] i40e: add helper conversion function for link_speed Jeff Kirsher
2018-01-03 21:22 ` [net-next 08/15] i40e/i40evf: Bump driver versions Jeff Kirsher
2018-01-03 21:22 ` [net-next 09/15] i40e: remove redundant initialization of read_size Jeff Kirsher
2018-01-03 21:22 ` [net-next 10/15] i40evf: Do not clear MSI-X PBA manually Jeff Kirsher
2018-01-03 21:22 ` [net-next 11/15] i40evf: Clean-up flags for promisc mode to avoid high polling rate Jeff Kirsher
2018-01-03 21:22 ` [net-next 12/15] i40evf: Drop i40evf_fire_sw_int as it is prone to races Jeff Kirsher
2018-01-04 9:31 ` Sergei Shtylyov [this message]
2018-01-04 17:51 ` Alexander Duyck
2018-01-04 18:46 ` David Miller
2018-01-03 21:22 ` [net-next 13/15] i40e: change ppp name to ddp Jeff Kirsher
2018-01-03 21:22 ` [net-next 14/15] i40e: track id can be 0 Jeff Kirsher
2018-01-03 21:22 ` [net-next 15/15] i40e: link_down_on_close private flag support Jeff Kirsher
2018-01-04 15:11 ` [net-next 00/15][pull request] 40GbE Intel Wired LAN Driver Updates 2018-01-03 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=2d470a24-a79e-b0f4-3a91-5f2dd0be5da0@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox