From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: edward.cree@amd.com
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
Edward Cree <ecree.xilinx@gmail.com>,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com
Subject: Re: [PATCH net-next 2/5] sfc: handle enc keys in efx_tc_flower_parse_match()
Date: Wed, 15 Mar 2023 10:01:41 +0100 [thread overview]
Message-ID: <ZBGJdWyXZSlXwN96@localhost.localdomain> (raw)
In-Reply-To: <962d11de229400416804173b2ab035d73493a6b4.1678815095.git.ecree.xilinx@gmail.com>
On Tue, Mar 14, 2023 at 05:35:22PM +0000, edward.cree@amd.com wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> Translate the fields from flow dissector into struct efx_tc_match.
> In efx_tc_flower_replace(), reject filters that match on them, because
> only 'foreign' filters (i.e. those for which the ingress dev is not
> the sfc netdev or any of its representors, e.g. a tunnel netdev) can
> use them.
>
> Signed-off-by: Edward Cree <ecree.xilinx@gmail.com>
> ---
> drivers/net/ethernet/sfc/tc.c | 65 +++++++++++++++++++++++++++++++++++
> 1 file changed, 65 insertions(+)
>
> diff --git a/drivers/net/ethernet/sfc/tc.c b/drivers/net/ethernet/sfc/tc.c
> index 2b07bb2fd735..d683665a8d87 100644
> --- a/drivers/net/ethernet/sfc/tc.c
> +++ b/drivers/net/ethernet/sfc/tc.c
> @@ -193,6 +193,11 @@ static int efx_tc_flower_parse_match(struct efx_nic *efx,
> BIT(FLOW_DISSECTOR_KEY_IPV4_ADDRS) |
> BIT(FLOW_DISSECTOR_KEY_IPV6_ADDRS) |
> BIT(FLOW_DISSECTOR_KEY_PORTS) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_KEYID) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_IPV4_ADDRS) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_IPV6_ADDRS) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_PORTS) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_CONTROL) |
> BIT(FLOW_DISSECTOR_KEY_TCP) |
> BIT(FLOW_DISSECTOR_KEY_IP))) {
> NL_SET_ERR_MSG_FMT_MOD(extack, "Unsupported flower keys %#x",
> @@ -280,6 +285,61 @@ static int efx_tc_flower_parse_match(struct efx_nic *efx,
> MAP_KEY_AND_MASK(PORTS, ports, src, l4_sport);
> MAP_KEY_AND_MASK(PORTS, ports, dst, l4_dport);
> MAP_KEY_AND_MASK(TCP, tcp, flags, tcp_flags);
> + if (flow_rule_match_key(rule, FLOW_DISSECTOR_KEY_ENC_CONTROL)) {
> + struct flow_match_control fm;
> +
> + flow_rule_match_enc_control(rule, &fm);
> + if (fm.mask->flags) {
> + NL_SET_ERR_MSG_FMT_MOD(extack, "Unsupported match on enc_control.flags %#x",
> + fm.mask->flags);
> + return -EOPNOTSUPP;
> + }
> + if (!IS_ALL_ONES(fm.mask->addr_type)) {
> + NL_SET_ERR_MSG_FMT_MOD(extack, "Unsupported enc addr_type mask %u (key %u)",
> + fm.mask->addr_type,
> + fm.key->addr_type);
> + return -EOPNOTSUPP;
> + }
> + switch (fm.key->addr_type) {
> + case FLOW_DISSECTOR_KEY_IPV4_ADDRS:
> + MAP_ENC_KEY_AND_MASK(IPV4_ADDRS, ipv4_addrs, enc_ipv4_addrs,
> + src, enc_src_ip);
> + MAP_ENC_KEY_AND_MASK(IPV4_ADDRS, ipv4_addrs, enc_ipv4_addrs,
> + dst, enc_dst_ip);
> + break;
> +#ifdef CONFIG_IPV6
> + case FLOW_DISSECTOR_KEY_IPV6_ADDRS:
> + MAP_ENC_KEY_AND_MASK(IPV6_ADDRS, ipv6_addrs, enc_ipv6_addrs,
> + src, enc_src_ip6);
> + MAP_ENC_KEY_AND_MASK(IPV6_ADDRS, ipv6_addrs, enc_ipv6_addrs,
> + dst, enc_dst_ip6);
> + break;
> +#endif
> + default:
> + NL_SET_ERR_MSG_FMT_MOD(extack,
> + "Unsupported enc addr_type %u (supported are IPv4, IPv6)",
> + fm.key->addr_type);
> + return -EOPNOTSUPP;
> + }
> +#if !defined(EFX_USE_KCOMPAT) || defined(EFX_HAVE_FLOW_DISSECTOR_KEY_ENC_IP)
Are these defines already in kernel, or You want to add it to kconfig?
I can't find it in tree, aren't they some kind of OOT driver defines?
> + MAP_ENC_KEY_AND_MASK(IP, ip, enc_ip, tos, enc_ip_tos);
> + MAP_ENC_KEY_AND_MASK(IP, ip, enc_ip, ttl, enc_ip_ttl);
> +#endif
> + MAP_ENC_KEY_AND_MASK(PORTS, ports, enc_ports, src, enc_sport);
> + MAP_ENC_KEY_AND_MASK(PORTS, ports, enc_ports, dst, enc_dport);
> + MAP_ENC_KEY_AND_MASK(KEYID, enc_keyid, enc_keyid, keyid, enc_keyid);
> + } else if (dissector->used_keys &
> + (BIT(FLOW_DISSECTOR_KEY_ENC_KEYID) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_IPV4_ADDRS) |
> + BIT(FLOW_DISSECTOR_KEY_ENC_IPV6_ADDRS) |
> +#if !defined(EFX_USE_KCOMPAT) || defined(EFX_HAVE_FLOW_DISSECTOR_KEY_ENC_IP)
> + BIT(FLOW_DISSECTOR_KEY_ENC_IP) |
> +#endif
> + BIT(FLOW_DISSECTOR_KEY_ENC_PORTS))) {
> + NL_SET_ERR_MSG_FMT_MOD(extack, "Flower enc keys require enc_control (keys: %#x)",
> + dissector->used_keys);
> + return -EOPNOTSUPP;
> + }
>
> return 0;
> }
> @@ -373,6 +433,11 @@ static int efx_tc_flower_replace(struct efx_nic *efx,
> rc = efx_tc_flower_parse_match(efx, fr, &match, extack);
> if (rc)
> return rc;
> + if (efx_tc_match_is_encap(&match.mask)) {
> + NL_SET_ERR_MSG_MOD(extack, "Ingress enc_key matches not supported");
> + rc = -EOPNOTSUPP;
> + goto release;
> + }
>
> if (tc->common.chain_index) {
> NL_SET_ERR_MSG_MOD(extack, "No support for nonzero chain_index");
next prev parent reply other threads:[~2023-03-15 9:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:35 [PATCH net-next 0/5] sfc: support TC decap rules edward.cree
2023-03-14 17:35 ` [PATCH net-next 1/5] sfc: add notion of match on enc keys to MAE machinery edward.cree
2023-03-15 6:19 ` Michal Swiatkowski
2023-03-15 13:45 ` Edward Cree
2023-03-14 17:35 ` [PATCH net-next 2/5] sfc: handle enc keys in efx_tc_flower_parse_match() edward.cree
2023-03-15 9:01 ` Michal Swiatkowski [this message]
2023-03-15 13:48 ` Edward Cree
2023-03-14 17:35 ` [PATCH net-next 3/5] sfc: add functions to insert encap matches into the MAE edward.cree
2023-03-15 9:23 ` Michal Swiatkowski
2023-03-15 13:58 ` Edward Cree
2023-03-14 17:35 ` [PATCH net-next 4/5] sfc: add code to register and unregister encap matches edward.cree
2023-03-15 9:43 ` Michal Swiatkowski
2023-03-15 14:01 ` Edward Cree
2023-03-14 17:35 ` [PATCH net-next 5/5] sfc: add offloading of 'foreign' TC (decap) rules edward.cree
2023-03-14 20:29 ` kernel test robot
2023-03-15 10:11 ` Michal Swiatkowski
2023-03-15 14:43 ` Edward Cree
2023-03-22 22:35 ` Edward Cree
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=ZBGJdWyXZSlXwN96@localhost.localdomain \
--to=michal.swiatkowski@linux.intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).