From: Simon Horman <horms@kernel.org>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
stable@vger.kernel.org,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net] ice: fix VF interrupts cleanup
Date: Tue, 19 May 2026 17:56:44 +0100 [thread overview]
Message-ID: <20260519165644.GI98116@horms.kernel.org> (raw)
In-Reply-To: <20260514163555.8243-1-dawid.osuchowski@linux.intel.com>
On Thu, May 14, 2026 at 06:35:55PM +0200, Dawid Osuchowski wrote:
> When a virtual function sends an IRQ map command, the PF will set up
> interrupts according to that request. However, because these interrupts are
> never reset, the next time Virtual Function initializes, the interrupts are
> still enabled for a given VF, which leads to performance degradation in
> certain cases (e.g. Data Plane Development Kit) due to interrupts being
> unexpectedly enabled and thus causing interrupt floods.
>
> Cc: stable@vger.kernel.org
> Fixes: 1071a8358a28 ("ice: Implement virtchnl commands for AVF support")
> Suggested-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> Signed-off-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
stable@vger.kernel.org,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [PATCH iwl-net] ice: fix VF interrupts cleanup
Date: Tue, 19 May 2026 17:56:44 +0100 [thread overview]
Message-ID: <20260519165644.GI98116@horms.kernel.org> (raw)
In-Reply-To: <20260514163555.8243-1-dawid.osuchowski@linux.intel.com>
On Thu, May 14, 2026 at 06:35:55PM +0200, Dawid Osuchowski wrote:
> When a virtual function sends an IRQ map command, the PF will set up
> interrupts according to that request. However, because these interrupts are
> never reset, the next time Virtual Function initializes, the interrupts are
> still enabled for a given VF, which leads to performance degradation in
> certain cases (e.g. Data Plane Development Kit) due to interrupts being
> unexpectedly enabled and thus causing interrupt floods.
>
> Cc: stable@vger.kernel.org
> Fixes: 1071a8358a28 ("ice: Implement virtchnl commands for AVF support")
> Suggested-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> Signed-off-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-05-19 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 16:35 [PATCH iwl-net] ice: fix VF interrupts cleanup Dawid Osuchowski
2026-05-14 16:35 ` [Intel-wired-lan] " Dawid Osuchowski
2026-05-19 16:56 ` Simon Horman [this message]
2026-05-19 16:56 ` Simon Horman
2026-06-03 8:54 ` [Intel-wired-lan] " Holda, Patryk
2026-06-03 8:54 ` Holda, Patryk
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=20260519165644.GI98116@horms.kernel.org \
--to=horms@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=dawid.osuchowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vladimir.medvedkin@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 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.