From: Zhang Tengfei <zhtfdev@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, jiawenwu@trustnetic.com, zaiyuwang@trustnetic.com
Subject: Re: [PATCH 0/3] net/txgbe: fix FDIR Rx packet buffer handling
Date: Thu, 15 Oct 2026 00:45:00 +0800 [thread overview]
Message-ID: <3de75531-dd3f-4953-8fb8-1f654b74f050@gmail.com> (raw)
In-Reply-To: <20261013074555.1ab5dc7c@phoenix.local>
On 10/13/26 22:45, Stephen Hemminger wrote:
> On Tue, 13 Oct 2026 22:00:16 +0800
> Zhang Tengfei <zhtfdev@gmail.com> wrote:
> [PATCH 2/3] net/txgbe: do not enable flow director on flow validate
>
> Warning: validate now accepts rules that create will always reject.
>
> txgbe_parse_fdir_filter_normal() can set
> rule->mode = RTE_FDIR_MODE_PERFECT_MAC_VLAN. Before this patch, with
> mode NONE, parse called txgbe_fdir_configure() which returns -ENOSYS
> for anything other than SIGNATURE or PERFECT, so validate failed.
> Now parse only checks for a mode mismatch, validate succeeds, and
> create fails later in txgbe_fdir_configure().
>
> Keep the cheap mode check in parse so validate and create agree:
>
> if (rule->mode != RTE_FDIR_MODE_SIGNATURE &&
> rule->mode != RTE_FDIR_MODE_PERFECT)
> return -ENOTSUP;
>
> if (fdir_conf->mode != RTE_FDIR_MODE_NONE &&
> fdir_conf->mode != rule->mode)
> return -ENOTSUP;
>
> [PATCH 3/3] net/txgbe: disable flow director when no rule is left
>
> Info: txgbe_fdir_disable() restores a single packet buffer layout
> (PB0 = rx_pb_size, PB1-7 = 0), not what txgbe_configure_dcb() set at
> dev_start. That matches what txgbe_fdir_configure() already does, so
> FDIR with DCB is already broken and this is not a new problem. If
> you respin, consider saving the PBRXSIZE values before enabling FDIR
> and restoring them on disable, or reject FDIR when DCB Rx is
> configured.
Thanks for review.
Addressed in v2.
2/3 now rejects modes other than signature and perfect while
parsing, so validate and create both fail for a MAC VLAN rule.
On 3/3 I left the DCB packet buffer as it is. Enabling FDIR
already clears PBRXSIZE(1..7). Rejecting FDIR when DCB Rx is
configured can be a separate patch.
next prev parent reply other threads:[~2026-10-14 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 14:00 [PATCH 0/3] net/txgbe: fix FDIR Rx packet buffer handling Zhang Tengfei
2026-10-13 14:00 ` [PATCH 1/3] net/txgbe: fix Rx packet buffer size with flow director Zhang Tengfei
2026-10-13 14:00 ` [PATCH 2/3] net/txgbe: do not enable flow director on flow validate Zhang Tengfei
2026-10-13 14:00 ` [PATCH 3/3] net/txgbe: disable flow director when no rule is left Zhang Tengfei
2026-10-13 14:45 ` [PATCH 0/3] net/txgbe: fix FDIR Rx packet buffer handling Stephen Hemminger
2026-10-14 16:45 ` Zhang Tengfei [this message]
2026-10-14 1:39 ` Jiawen Wu
2026-10-14 16:47 ` Zhang Tengfei
2026-10-14 16:39 ` [PATCH v2 " Zhang Tengfei
2026-10-14 16:39 ` [PATCH v2 1/3] net/txgbe: fix Rx packet buffer size with flow director Zhang Tengfei
2026-10-14 16:39 ` [PATCH v2 2/3] net/txgbe: do not enable flow director on flow validate Zhang Tengfei
2026-10-14 16:39 ` [PATCH v2 3/3] net/txgbe: disable flow director when no rule is left Zhang Tengfei
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=3de75531-dd3f-4953-8fb8-1f654b74f050@gmail.com \
--to=zhtfdev@gmail.com \
--cc=dev@dpdk.org \
--cc=jiawenwu@trustnetic.com \
--cc=stephen@networkplumber.org \
--cc=zaiyuwang@trustnetic.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