DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Zhang Tengfei <zhtfdev@gmail.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH] net/ixgbe: fix repeated Rx packet buffer shrink for FDIR
Date: Fri, 25 Sep 2026 11:47:16 +0200	[thread overview]
Message-ID: <a46db9e8-1513-4e19-b029-2d55e28d42b4@intel.com> (raw)
In-Reply-To: <20260916135827.116145-1-zhtfdev@gmail.com>

On 9/16/2026 3:58 PM, 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>
> ---

A general comment: instead of reducing/bringing things back and storing 
a flag noting whether we did, I would rather do the following:

0) store default rx pb size at init
1) on enabling FDIR, recalculate using that value minus FDIR table size
2) on disabling FDIR[*], restore the default
3) similarly, on enable/disable VMDq, recalculate and/or reset

[*] there is no "disable FDIR" call, only fdir flush which just flushes 
the FDIR tables but does not actually disable FDIR. arguably, we should 
convert it to "disable FDIR" by flushing FDIR *and* writing 0 to 
FDIRCTRL *and* restoring rx pb size to defaults. naturally, after 
running fdir disable function, FDIR will need to be reconfigured for 
next FDIR flow and get rx pb size recalculated again.

So, a bit of a refactor, but I think that would make way more sense.

-- 
Thanks,
Anatoly

  parent reply	other threads:[~2026-09-25  9:47 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
2026-09-25  9:47 ` Burakov, Anatoly [this message]
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=a46db9e8-1513-4e19-b029-2d55e28d42b4@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@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