From: Kurt Kanzenbach <kurt@linutronix.de>
To: "Behera, VIVEK" <vivek.behera@siemens.com>,
"Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
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>
Cc: "intel-wired-lan@lists.osuosl.org" <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH v5 iwl-net] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function
Date: Wed, 10 Dec 2025 15:34:46 +0100 [thread overview]
Message-ID: <87tsxymmm1.fsf@jax.kurt.home> (raw)
In-Reply-To: <AS1PR10MB5392E7164825969656D966CB8FA0A@AS1PR10MB5392.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]
On Wed Dec 10 2025, Behera, VIVEK wrote:
> On Wed Dec 10 2025, Kurt Kanzenbach wrote:
>> On Wed Dec 10 2025, Behera, VIVEK wrote:
>>> Changes in v5:
>>> - Updated comment style from multi-star to standard /* */ as suggested by Aleksandr.
>>>
>>> From ab2583ff8a17405d3aa6caf4df1c4fdfb21f5e98 Mon Sep 17 00:00:00 2001
>>> From: Vivek Behera <vivek.behera@siemens.com>
>>> Date: Fri, 5 Dec 2025 10:26:05 +0100
>>> Subject: [PATCH v5] [iwl-net] igc: Fix trigger of incorrect irq in
>>> igc_xsk_wakeup function
>>>
>>> This patch addresses the issue where the igc_xsk_wakeup function was
>>> triggering an incorrect IRQ for tx-0 when the i226 is configured with
>>> only 2 combined queues or in an environment with 2 active CPU cores.
>>> This prevented XDP Zero-copy send functionality in such split IRQ
>>> configurations.
>>>
>>> The fix implements the correct logic for extracting q_vectors saved
>>> during rx and tx ring allocation and utilizes flags provided by the
>>> ndo_xsk_wakeup API to trigger the appropriate IRQ.
>>>
>>> Changed comment blocks to align with standard Linux comments
>>>
>>> Fixes: fc9df2a0b520d7d439ecf464794d53e91be74b93 ("igc: Enable RX via
>>> AF_XDP zero-copy")
>>> Fixes: 15fd021bc4270273d8f4b7f58fdda8a16214a377 ("igc: Add Tx hardware
>>> timestamp request for AF_XDP zero-copy packet")
>>> Signed-off-by: Vivek Behera <vivek.behera@siemens.com>
>>> Reviewed-by: Jacob Keller <jacob.keller@intel.com>
>>> Reviewed-by: Aleksandr loktinov <aleksandr.loktionov@intel.com>
>>
>> Hi,
>>
>> thanks for this fix. Does the same issue also exist for i210 in the igb driver? The igb driver also has this split IRQ configuration with 2 queues. Might be good to fix this one as well :).
>>
>> Thanks,
>> Kurt
>
> Hi Kurt,
>
> The issue so far has not popped up in i210 igb driver for XDP ZC send
> but will impact the xsk_wakeup attempting to wakeup the RX irqs or
> both Rx and Tx (for.e.g in xsk_poll) if IRQ configuration is with 2
> queues. Essentially same logic submitted in the patch is needed for
> igb. I am preparing a patch for the igb aswell. However, I would wait
> for submission until I manage to resolve the formatting and other
> guideline related issue pointed out by Jakub in the igc patch.
Sounds great. Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2025-12-10 14:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 12:39 [Intel-wired-lan] [PATCH] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function Behera, VIVEK
2025-12-05 12:39 ` Behera, VIVEK
2025-12-05 21:05 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-12-06 12:03 ` Behera, VIVEK
2025-12-06 12:03 ` Behera, VIVEK
2025-12-07 15:46 ` [Intel-wired-lan] [PATCH v2] igc: Enhance xsk wakeup for split IRQ and fix PTP TX wakeup Behera, VIVEK
2025-12-07 15:46 ` Behera, VIVEK
2025-12-08 23:53 ` [Intel-wired-lan] [PATCH] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function Jacob Keller
2025-12-08 23:53 ` Jacob Keller
2025-12-09 6:03 ` [Intel-wired-lan] " Behera, VIVEK
2025-12-09 6:03 ` Behera, VIVEK
2025-12-09 6:46 ` [Intel-wired-lan] [PATCH v3 iwl-net] " Behera, VIVEK
2025-12-09 6:46 ` Behera, VIVEK
2025-12-09 8:05 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-12-09 8:05 ` Loktionov, Aleksandr
2025-12-10 7:09 ` [Intel-wired-lan] [PATCH v4 " Behera, VIVEK
2025-12-10 7:09 ` AW: " Behera, VIVEK
2025-12-10 7:16 ` [Intel-wired-lan] [PATCH v3 " Loktionov, Aleksandr
2025-12-10 7:16 ` Loktionov, Aleksandr
2025-12-10 7:50 ` [Intel-wired-lan] [PATCH v5 " Behera, VIVEK
2025-12-10 7:50 ` AW: " Behera, VIVEK
2025-12-10 8:57 ` [Intel-wired-lan] " Jakub Kicinski
2025-12-10 8:57 ` Jakub Kicinski
2025-12-10 10:16 ` [Intel-wired-lan] " Kurt Kanzenbach
2025-12-10 10:16 ` AW: " Kurt Kanzenbach
2025-12-10 10:48 ` [Intel-wired-lan] " Behera, VIVEK
2025-12-10 14:34 ` Kurt Kanzenbach [this message]
2025-12-10 16:41 ` Paul Menzel
2025-12-10 10:15 ` [Intel-wired-lan] [PATCH v3 " Kwapulinski, Piotr
2025-12-10 10:15 ` Kwapulinski, Piotr
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=87tsxymmm1.fsf@jax.kurt.home \
--to=kurt@linutronix.de \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=vivek.behera@siemens.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.