From: Ido Schimmel <idosch@idosch.org>
To: Zahari Doychev <zahari.doychev@linux.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
hmehrtens@maxlinear.com, aleksander.lobakin@intel.com,
simon.horman@corigine.com,
Zahari Doychev <zdoychev@maxlinear.com>
Subject: Re: [PATCH net-next v6 2/3] net: flower: add support for matching cfm fields
Date: Wed, 7 Jun 2023 10:12:26 +0300 [thread overview]
Message-ID: <ZIAt2gCBOBn8sfOj@shredder> (raw)
In-Reply-To: <20230606205935.570850-3-zahari.doychev@linux.com>
On Tue, Jun 06, 2023 at 10:59:34PM +0200, Zahari Doychev wrote:
> From: Zahari Doychev <zdoychev@maxlinear.com>
>
> Add support to the tc flower classifier to match based on fields in CFM
> information elements like level and opcode.
>
> tc filter add dev ens6 ingress protocol 802.1q \
> flower vlan_id 698 vlan_ethtype 0x8902 cfm mdl 5 op 46 \
> action drop
Looks good overall. One minor comment below.
[...]
> +static int fl_set_key_cfm_md_level(struct nlattr **tb,
> + struct fl_flow_key *key,
> + struct fl_flow_key *mask,
> + struct netlink_ext_ack *extack)
> +{
> + u8 level;
> +
> + if (!tb[TCA_FLOWER_KEY_CFM_MD_LEVEL])
> + return 0;
> +
> + level = nla_get_u8(tb[TCA_FLOWER_KEY_CFM_MD_LEVEL]);
> + key->cfm.mdl_ver = FIELD_PREP(FLOW_DIS_CFM_MDL_MASK, level);
> + mask->cfm.mdl_ver = FLOW_DIS_CFM_MDL_MASK;
> +
> + return 0;
> +}
This function always returns '0' so it can be changed to return 'void'
instead of 'int' like fl_set_key_cfm_opcode().
> +
> +static void fl_set_key_cfm_opcode(struct nlattr **tb,
> + struct fl_flow_key *key,
> + struct fl_flow_key *mask,
> + struct netlink_ext_ack *extack)
> +{
> + fl_set_key_val(tb, &key->cfm.opcode, TCA_FLOWER_KEY_CFM_OPCODE,
> + &mask->cfm.opcode, TCA_FLOWER_UNSPEC,
> + sizeof(key->cfm.opcode));
> +}
> +
> +static int fl_set_key_cfm(struct nlattr **tb,
> + struct fl_flow_key *key,
> + struct fl_flow_key *mask,
> + struct netlink_ext_ack *extack)
> +{
> + struct nlattr *nla_cfm_opt[TCA_FLOWER_KEY_CFM_OPT_MAX];
> + int err;
> +
> + if (!tb[TCA_FLOWER_KEY_CFM])
> + return 0;
> +
> + err = nla_parse_nested(nla_cfm_opt, TCA_FLOWER_KEY_CFM_OPT_MAX,
> + tb[TCA_FLOWER_KEY_CFM], cfm_opt_policy, extack);
> + if (err < 0)
> + return err;
> +
> + fl_set_key_cfm_opcode(nla_cfm_opt, key, mask, extack);
> +
> + return fl_set_key_cfm_md_level(nla_cfm_opt, key, mask, extack);
And here simply do 'return 0;'.
> +}
next prev parent reply other threads:[~2023-06-07 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 20:59 [PATCH net-next v6 0/3] net: flower: add cfm support Zahari Doychev
2023-06-06 20:59 ` [PATCH net-next v6 1/3] net: flow_dissector: add support for cfm packets Zahari Doychev
2023-06-06 20:59 ` [PATCH net-next v6 2/3] net: flower: add support for matching cfm fields Zahari Doychev
2023-06-07 7:12 ` Ido Schimmel [this message]
2023-06-06 20:59 ` [PATCH net-next v6 3/3] selftests: net: add tc flower cfm test Zahari Doychev
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=ZIAt2gCBOBn8sfOj@shredder \
--to=idosch@idosch.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hmehrtens@maxlinear.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=xiyou.wangcong@gmail.com \
--cc=zahari.doychev@linux.com \
--cc=zdoychev@maxlinear.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;
as well as URLs for NNTP newsgroup(s).