From: Simon Horman <horms@kernel.org>
To: xiaoliang.yang_1@nxp.com
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jhs@mojatatu.com, jiri@resnulli.us, shuah@kernel.org,
vladimir.oltean@nxp.com, vinicius.gomes@intel.com,
fejes@inf.elte.hu
Subject: Re: [PATCH net-next 3/6] uapi: tc_act: add tc_frer UAPI header
Date: Fri, 24 Jul 2026 12:49:07 +0100 [thread overview]
Message-ID: <20260724114906.667323-2-horms@kernel.org> (raw)
In-Reply-To: <20260717095549.10565-4-xiaoliang.yang_1@nxp.com>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
Full review at: https://sashiko.dev/#/patchset/20260717095549.10565-3-xiaoliang.yang_1@nxp.com?part=3
---
--- Patch [3]: [PATCH net-next 3/6] uapi: tc_act: add tc_frer UAPI header ---
commit 070d4b29514ff2aff8a973818dd8d51372a699d4
Author: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
uapi: tc_act: add tc_frer UAPI header
This commit defines the netlink attribute layout and enumerations for the
FRER tc action (IEEE 802.1CB). It introduces functional sub-commands,
recovery configurations, and read-only statistics.
> diff --git a/include/uapi/linux/tc_act/tc_frer.h b/include/uapi/linux/tc_act/tc_frer.h
> new file mode 100644
> index 0000000000000..241e90827e262
> --- /dev/null
> +++ b/include/uapi/linux/tc_act/tc_frer.h
[ ... ]
> +enum {
> + TCA_FRER_UNSPEC,
> + TCA_FRER_TM, /* struct tcf_t */
> + TCA_FRER_PARMS, /* struct tc_frer */
> + TCA_FRER_PAD,
> + TCA_FRER_FUNC, /* u8: tc_frer_func */
> + TCA_FRER_TAG_TYPE, /* u8: tc_frer_tag_type */
> + TCA_FRER_RCVY_INDIVIDUAL, /* NLA_FLAG */
> + TCA_FRER_RCVY_ALG, /* u8: tc_frer_rcvy_alg */
> + TCA_FRER_RCVY_HISTORY_LEN, /* u8: 1-32 */
[Severity: Medium]
Are these u8 attributes necessary here, or should they be u32? The Netlink
UAPI guidelines recommend avoiding integer types smaller than 32 bits for
attributes. They save no memory due to the 4-byte attribute alignment and
using smaller types unnecessarily restricts future extensibility.
next prev parent reply other threads:[~2026-07-24 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 9:55 [PATCH net-next 0/6] tc: introduce FRER action (IEEE 802.1CB) Xiaoliang Yang
2026-07-17 9:55 ` [PATCH net-next 1/6] uapi: if_ether: add ETH_P_RTAG for IEEE 802.1CB R-TAG Xiaoliang Yang
2026-07-17 9:55 ` [PATCH net-next 2/6] uapi: pkt_cls: add TCA_ID_FRER action identifier Xiaoliang Yang
2026-07-17 9:55 ` [PATCH net-next 3/6] uapi: tc_act: add tc_frer UAPI header Xiaoliang Yang
2026-07-24 11:49 ` Simon Horman [this message]
2026-07-17 9:55 ` [PATCH net-next 4/6] net: sched: act_frer: add FRER tc action Xiaoliang Yang
2026-07-24 12:33 ` Simon Horman
2026-07-17 9:55 ` [PATCH net-next 5/6] selftest: add tc-testing JSON test cases for act_frer Xiaoliang Yang
2026-07-24 12:34 ` Simon Horman
2026-07-17 9:55 ` [PATCH net-next 6/6] selftests: net: add kselftest for IEEE 802.1CB FRER tc action Xiaoliang Yang
2026-07-24 12:48 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2026-06-22 9:21 [PATCH net-next 0/6] tc: introduce FRER action (IEEE 802.1CB) Xiaoliang Yang
2026-06-22 9:21 ` [PATCH net-next 3/6] uapi: tc_act: add tc_frer UAPI header Xiaoliang Yang
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=20260724114906.667323-2-horms@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fejes@inf.elte.hu \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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.