From: Kurt Kanzenbach <kurt@linutronix.de>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Joe Damato <jdamato@fastly.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH 3/3] igb: Get rid of spurious interrupts
Date: Tue, 11 Feb 2025 08:51:58 +0100 [thread overview]
Message-ID: <87y0ycor4x.fsf@kurt.kurt.home> (raw)
In-Reply-To: <b1b3e5e1-b1fe-4816-85eb-61ac7ea2d46d@engleder-embedded.com>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
On Mon Feb 10 2025, Gerhard Engleder wrote:
> On 10.02.25 10:19, Kurt Kanzenbach wrote:
>> When running the igc with XDP/ZC in busy polling mode with deferral of hard
>> interrupts, interrupts still happen from time to time. That is caused by
>> the igc task watchdog which triggers Rx interrupts periodically.
>
> igc or igb?
igb of course. Thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2025-02-11 7:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 9:19 [PATCH 0/3] igb: XDP/ZC follow up Kurt Kanzenbach
2025-02-10 9:19 ` [PATCH 1/3] igb: Link IRQs to NAPI instances Kurt Kanzenbach
2025-02-10 18:25 ` Joe Damato
2025-02-10 22:22 ` Joe Damato
2025-02-10 9:19 ` [PATCH 2/3] igb: Link queues " Kurt Kanzenbach
2025-02-10 18:47 ` Joe Damato
2025-02-11 7:51 ` Kurt Kanzenbach
2025-02-10 9:19 ` [PATCH 3/3] igb: Get rid of spurious interrupts Kurt Kanzenbach
2025-02-10 18:58 ` Joe Damato
2025-02-10 20:14 ` Gerhard Engleder
2025-02-11 7:51 ` Kurt Kanzenbach [this message]
2025-02-10 19:49 ` [PATCH 0/3] igb: XDP/ZC follow up Joe Damato
2025-02-11 3:15 ` Joe Damato
2025-02-11 14:44 ` Kurt Kanzenbach
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=87y0ycor4x.fsf@kurt.kurt.home \
--to=kurt@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).