From: Raslan Darawsheh <rasland@nvidia.com>
To: Li Zhang <lizh@nvidia.com>, Dekel Peled <dekelp@nvidia.com>,
Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v9 1/1] net/mlx5: support match ICMP identifier fields
Date: Sun, 11 Oct 2020 10:19:45 +0000 [thread overview]
Message-ID: <DM6PR12MB2748731F0A62469DBCFEE11BCF060@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201009061142.305-1-lizh@nvidia.com>
Hi,
> -----Original Message-----
> From: Li Zhang <lizh@nvidia.com>
> Sent: Friday, October 9, 2020 9:12 AM
> To: Dekel Peled <dekelp@nvidia.com>; Ori Kam <orika@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Cc: dev@dpdk.org; NBU-Contact-Thomas Monjalon
> <thomas@monjalon.net>; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v9 1/1] net/mlx5: support match ICMP identifier fields
>
> PRM expose fields "Icmp_header_data" in IPv4 ICMP.
> Update ICMP mask parameter with ICMP identifier and sequence number
> fields.
> ICMP sequence number spec with mask, Icmp_header_data low 16 bits are
> set.
> ICMP identifier spec with mask, Icmp_header_data high 16 bits are set.
>
> Signed-off-by: Li Zhang <lizh@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> ---
> doc/guides/nics/mlx5.rst | 4 ++--
> doc/guides/rel_notes/release_20_11.rst | 2 +-
> drivers/net/mlx5/mlx5_flow.c | 10 ++++++++--
> drivers/net/mlx5/mlx5_flow_dv.c | 13 +++++++++++++
> 4 files changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index b0614ae335..a174cdd5f5 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -288,7 +288,7 @@ Limitations
> - The input buffer, providing the removal size, is not validated.
> - The buffer size must match the length of the headers to be removed.
>
> -- ICMP/ICMP6 code/type matching, IP-in-IP and MPLS flow matching are all
> +- ICMP(code/type/identifier/sequence number) / ICMP6(code/type)
> matching, IP-in-IP and MPLS flow matching are all
> mutually exclusive features which cannot be supported together
> (see :ref:`mlx5_firmware_config`).
>
> @@ -1009,7 +1009,7 @@ Below are some firmware configurations listed.
>
> FLEX_PARSER_PROFILE_ENABLE=1
>
> -- enable ICMP/ICMP6 code/type fields matching::
> +- enable ICMP(code/type/identifier/sequence number) /
> ICMP6(code/type) fields matching::
>
> FLEX_PARSER_PROFILE_ENABLE=2
>
> diff --git a/doc/guides/rel_notes/release_20_11.rst
> b/doc/guides/rel_notes/release_20_11.rst
> index b0637640d1..e22e0c3981 100644
> --- a/doc/guides/rel_notes/release_20_11.rst
> +++ b/doc/guides/rel_notes/release_20_11.rst
> @@ -102,7 +102,7 @@ New Features
> * Added flag action.
> * Added raw encap/decap actions.
> * Added VXLAN encap/decap actions.
> - * Added ICMP and ICMP6 matching items.
> + * Added ICMP(code/type/identifier/sequence number) and
> ICMP6(code/type) matching items.
> * Added option to set port mask for insertion/deletion:
> ``--portmask=N``
> where N represents the hexadecimal bitmask of ports used.
> diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
> index 691eb9a3cd..0a54818c0c 100644
> --- a/drivers/net/mlx5/mlx5_flow.c
> +++ b/drivers/net/mlx5/mlx5_flow.c
> @@ -1629,6 +1629,12 @@ mlx5_flow_validate_item_icmp(const struct
> rte_flow_item *item,
> struct rte_flow_error *error)
> {
> const struct rte_flow_item_icmp *mask = item->mask;
> + const struct rte_flow_item_icmp nic_mask = {
> + .hdr.icmp_type = 0xff,
> + .hdr.icmp_code = 0xff,
> + .hdr.icmp_ident = RTE_BE16(0xffff),
> + .hdr.icmp_seq_nb = RTE_BE16(0xffff),
> + };
> const int tunnel = !!(item_flags & MLX5_FLOW_LAYER_TUNNEL);
> const uint64_t l3m = tunnel ? MLX5_FLOW_LAYER_INNER_L3_IPV4 :
> MLX5_FLOW_LAYER_OUTER_L3_IPV4;
> @@ -1651,10 +1657,10 @@ mlx5_flow_validate_item_icmp(const struct
> rte_flow_item *item,
> RTE_FLOW_ERROR_TYPE_ITEM,
> item,
> "multiple L4 layers not supported");
> if (!mask)
> - mask = &rte_flow_item_icmp_mask;
> + mask = &nic_mask;
> ret = mlx5_flow_item_acceptable
> (item, (const uint8_t *)mask,
> - (const uint8_t *)&rte_flow_item_icmp_mask,
> + (const uint8_t *)&nic_mask,
> sizeof(struct rte_flow_item_icmp), error);
> if (ret < 0)
> return ret;
> diff --git a/drivers/net/mlx5/mlx5_flow_dv.c
> b/drivers/net/mlx5/mlx5_flow_dv.c
> index 79fdf34c0e..2bbfcea1ed 100644
> --- a/drivers/net/mlx5/mlx5_flow_dv.c
> +++ b/drivers/net/mlx5/mlx5_flow_dv.c
> @@ -7378,6 +7378,8 @@ flow_dv_translate_item_icmp(void *matcher, void
> *key,
> {
> const struct rte_flow_item_icmp *icmp_m = item->mask;
> const struct rte_flow_item_icmp *icmp_v = item->spec;
> + uint32_t icmp_header_data_m = 0;
> + uint32_t icmp_header_data_v = 0;
> void *headers_m;
> void *headers_v;
> void *misc3_m = MLX5_ADDR_OF(fte_match_param, matcher,
> @@ -7412,6 +7414,17 @@ flow_dv_translate_item_icmp(void *matcher,
> void *key,
> icmp_m->hdr.icmp_code);
> MLX5_SET(fte_match_set_misc3, misc3_v, icmp_code,
> icmp_v->hdr.icmp_code & icmp_m->hdr.icmp_code);
> + icmp_header_data_m = rte_be_to_cpu_16(icmp_m-
> >hdr.icmp_seq_nb);
> + icmp_header_data_m |= rte_be_to_cpu_16(icmp_m-
> >hdr.icmp_ident) << 16;
> + if (icmp_header_data_m) {
> + icmp_header_data_v = rte_be_to_cpu_16(icmp_v-
> >hdr.icmp_seq_nb);
> + icmp_header_data_v |=
> + rte_be_to_cpu_16(icmp_v->hdr.icmp_ident) << 16;
> + MLX5_SET(fte_match_set_misc3, misc3_m,
> icmp_header_data,
> + icmp_header_data_m);
> + MLX5_SET(fte_match_set_misc3, misc3_v,
> icmp_header_data,
> + icmp_header_data_v & icmp_header_data_m);
> + }
> }
>
> /**
> --
> 2.21.0
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-10-11 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200930164734.23675-1-lizh@nvidia.co>
2020-10-02 8:40 ` [dpdk-dev] [PATCH v4 " Li Zhang
2020-10-04 11:59 ` Ori Kam
2020-10-05 9:20 ` Li Zhang
2020-10-05 9:41 ` Li Zhang
2020-10-05 9:18 ` [dpdk-dev] [PATCH v5 " Li Zhang
2020-10-05 9:31 ` [dpdk-dev] [PATCH v6 " Li Zhang
2020-10-05 10:33 ` Ori Kam
2020-10-06 5:12 ` Li Zhang
2020-10-06 12:07 ` Ori Kam
2020-10-07 6:08 ` Li Zhang
2020-10-09 6:01 ` [dpdk-dev] [PATCH v7 " Li Zhang
2020-10-09 6:06 ` [dpdk-dev] [PATCH v8 " Li Zhang
2020-10-09 6:11 ` [dpdk-dev] [PATCH v9 " Li Zhang
2020-10-11 10:19 ` Raslan Darawsheh [this message]
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=DM6PR12MB2748731F0A62469DBCFEE11BCF060@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dekelp@nvidia.com \
--cc=dev@dpdk.org \
--cc=lizh@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).