From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"przemyslaw.kitszel@intel.com" <przemyslaw.kitszel@intel.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"aleksander.lobakin@intel.com" <aleksander.lobakin@intel.com>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Blair Steven <Blair.Steven@alliedtelesis.co.nz>,
Carl Smith <Carl.Smith@alliedtelesis.co.nz>
Subject: Re: [PATCH net-next] i40e: Avoid repeating RX filter warning
Date: Thu, 30 Jul 2026 13:13:13 -0700 [thread overview]
Message-ID: <5f1456d9-a098-4459-8fe0-3a90c4db0ed3@intel.com> (raw)
In-Reply-To: <c2f3acdd-9985-4d8f-bfc4-5d83f520f4a9@alliedtelesis.co.nz>
On 7/29/2026 4:53 PM, Chris Packham wrote:
> Hi All,
>
> On 14/05/2026 12:37, Chris Packham wrote:
>> When the i40e runs out of space for RX filters the driver switches to
>> promiscuous mode and warns that it has done so. In scenarios with a
>> large number of these filters this can generate a lot of warnings. For
>> example:
>>
>> $ dmesg -c > /dev/null
>> $ ip link add dev br0 type bridge vlan_filtering 1 vlan_default_pvid 1
>> $ ip link set dev eth7 master br0
>> $ bridge vlan add vid 1 dev eth7 pvid untagged self
>> $ bridge vlan add vid 2-4094 dev eth7 tagged
>> $ dmesg
>> [ 25.601705] i40e 0000:01:00.1: Error LIBIE_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
>> [ 25.601833] i40e 0000:01:00.1: Error LIBIE_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
>> [ 25.601961] i40e 0000:01:00.1: Error LIBIE_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
>> [ 25.602088] i40e 0000:01:00.1: Error LIBIE_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
>> [ 25.602216] i40e 0000:01:00.1: Error LIBIE_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
>> [ 25.602344] i40e 0000:01:00.1: Error LIBIE_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
>> ...
>>
>> Use test_and_set_bit() so that the warning is only issued when the
>> driver enables promiscuous mode and not on the addition of subsequent RX
>> filters.
>>
>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
>> ---
>>
>> Resend with net-next tag
>
> Has this fallen through the cracks? I've seen some Reviewed-bys but it
> doesn't seem to have been picked up.
Hi Chris,
I have it in my queue of patches to send out but I'm working my way to
it. I do hope to have it sent on soon.
Thanks,
Tony
>>
>> drivers/net/ethernet/intel/i40e/i40e_main.c | 18 ++++++++++--------
>> 1 file changed, 10 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
>> index 926d001b2150..8741990b5a5e 100644
>> --- a/drivers/net/ethernet/intel/i40e/i40e_main.c
>> +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c
>> @@ -2408,10 +2408,11 @@ void i40e_aqc_add_filters(struct i40e_vsi *vsi, const char *vsi_name,
>>
>> if (fcnt != num_add) {
>> if (vsi->type == I40E_VSI_MAIN) {
>> - set_bit(__I40E_VSI_OVERFLOW_PROMISC, vsi->state);
>> - dev_warn(&vsi->back->pdev->dev,
>> - "Error %s adding RX filters on %s, promiscuous mode forced on\n",
>> - libie_aq_str(aq_status), vsi_name);
>> + if (!test_and_set_bit(__I40E_VSI_OVERFLOW_PROMISC, vsi->state)) {
>> + dev_warn(&vsi->back->pdev->dev,
>> + "Error %s adding RX filters on %s, promiscuous mode forced on\n",
>> + libie_aq_str(aq_status), vsi_name);
>> + }
>> } else if (vsi->type == I40E_VSI_SRIOV ||
>> vsi->type == I40E_VSI_VMDQ1 ||
>> vsi->type == I40E_VSI_VMDQ2) {
>> @@ -2461,10 +2462,11 @@ i40e_aqc_broadcast_filter(struct i40e_vsi *vsi, const char *vsi_name,
>> }
>>
>> if (aq_ret) {
>> - set_bit(__I40E_VSI_OVERFLOW_PROMISC, vsi->state);
>> - dev_warn(&vsi->back->pdev->dev,
>> - "Error %s, forcing overflow promiscuous on %s\n",
>> - libie_aq_str(hw->aq.asq_last_status), vsi_name);
>> + if (!test_and_set_bit(__I40E_VSI_OVERFLOW_PROMISC, vsi->state)) {
>> + dev_warn(&vsi->back->pdev->dev,
>> + "Error %s, forcing overflow promiscuous on %s\n",
>> + libie_aq_str(hw->aq.asq_last_status), vsi_name);
>> + }
>> }
>>
>> return aq_ret;
next prev parent reply other threads:[~2026-07-30 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 0:37 [PATCH net-next] i40e: Avoid repeating RX filter warning Chris Packham
2026-05-14 9:06 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-18 18:32 ` Simon Horman
2026-07-01 5:23 ` [Intel-wired-lan] " Rinitha, SX
2026-07-29 23:53 ` Chris Packham
2026-07-30 20:13 ` Tony Nguyen [this message]
2026-07-30 20:48 ` Chris Packham
2026-07-30 13:52 ` [Intel-wired-lan] " Loktionov, Aleksandr
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=5f1456d9-a098-4459-8fe0-3a90c4db0ed3@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=Blair.Steven@alliedtelesis.co.nz \
--cc=Carl.Smith@alliedtelesis.co.nz \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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