DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Zhang Tengfei <zhtfdev@gmail.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>, <dev@dpdk.org>,
	<stable@dpdk.org>
Subject: Re: [PATCH] net/ixgbe: fix repeated Rx packet buffer shrink for FDIR
Date: Fri, 18 Sep 2026 14:50:38 +0100	[thread overview]
Message-ID: <aq1BruyBz4euARRM@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260916135827.116145-1-zhtfdev@gmail.com>

On Wed, Sep 16, 2026 at 09:58:27PM +0800, Zhang Tengfei wrote:
> Enabling Flow Director reduces RXPBSIZE to reserve SRAM for the
> filter table. Clearing the last FDIR rule set the mode back to
> none without restoring that buffer, so the next flow create ran
> configure again and subtracted the same amount a second time.
> 
> Keep the FDIR mode after rules are removed, and subtract RXPBSIZE
> only once until the next hardware reset.
> 
> Fixes: 301abd26b118 ("net/ixgbe: reset flow state on clear paths")
> Cc: stable@dpdk.org
> Signed-off-by: Zhang Tengfei <zhtfdev@gmail.com>
> ---
>  drivers/net/intel/ixgbe/ixgbe_ethdev.c |  7 +++++--
>  drivers/net/intel/ixgbe/ixgbe_ethdev.h |  1 +
>  drivers/net/intel/ixgbe/ixgbe_fdir.c   | 21 ++++++++++++++-------
>  drivers/net/intel/ixgbe/ixgbe_flow.c   |  1 -
>  4 files changed, 20 insertions(+), 10 deletions(-)
> 
Reviewing this patch, I'm wondering if this approach is actually the best
way to fix this. For example, after this change, if flow director is used
and then all rules removed, the flow director mode is still preserved,
possibly preventing use of other features that conflict with the old fdir
mode.

I wonder if a cleaner fix - which should be shorter too - might be to
instead just restore the RXPBSIZE value back when the fdir mode is set to
NONE. This gives a clean combination of (enable + set RXPBSIZE0) and (disable +
reset RXPBSIZE).

What do you think?

/Bruce

  reply	other threads:[~2026-09-18 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 13:58 [PATCH] net/ixgbe: fix repeated Rx packet buffer shrink for FDIR Zhang Tengfei
2026-09-18 13:50 ` Bruce Richardson [this message]
2026-09-25  9:47 ` Burakov, Anatoly
2026-09-25 10:05   ` Burakov, Anatoly
2026-09-25 18:59     ` Zhang Tengfei
2026-09-27  4:25 ` [PATCH v2] " Zhang Tengfei
2026-10-06  9:23   ` Burakov, Anatoly
2026-10-06  9:51     ` Bruce Richardson

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=aq1BruyBz4euARRM@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=vladimir.medvedkin@intel.com \
    --cc=zhtfdev@gmail.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