DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: psatheesh@marvell.com
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	 Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] common/cnxk: fix issue with IPv6 ext matching
Date: Thu, 12 Jan 2023 19:02:19 +0530	[thread overview]
Message-ID: <CALBAE1Mo2ExiAGc8yrF9zerzt_TZsCWdxRWmmZB1uG8eM6_-8Q@mail.gmail.com> (raw)
In-Reply-To: <20230112063620.1057554-1-psatheesh@marvell.com>

On Thu, Jan 12, 2023 at 12:06 PM <psatheesh@marvell.com> wrote:
>
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> While configuring ipv6 flow, ipv6 ext ltype should be
> matched along with ipv6. Adding changes to fix this issue.
>
> Fixes: 474e275b1bc6 ("common/cnxk: support extensions attributes in IPv6 item")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> Reviewed-by: Satheesh Paul <psatheesh@marvell.com>


Updated the git commit as follows and applied to
dpdk-next-net-mrvl/for-next-net. Thanks

    common/cnxk: fix issue with IPv6 ext matching

    While configuring IPv6 flow, IPv6 ext ltype should be
    matched along with IPv6. Adding changes to fix this issue.

    Fixes: 474e275b1bc6 ("common/cnxk: support extensions attributes
in IPv6 item")
    Cc: stable@dpdk.org

    Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
    Reviewed-by: Satheesh Paul <psatheesh@marvell.com>


> ---
>  drivers/common/cnxk/roc_npc_mcam.c | 19 ++++++++++---------
>  1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/common/cnxk/roc_npc_mcam.c b/drivers/common/cnxk/roc_npc_mcam.c
> index c419ce3a4c..0abd8872b1 100644
> --- a/drivers/common/cnxk/roc_npc_mcam.c
> +++ b/drivers/common/cnxk/roc_npc_mcam.c
> @@ -727,15 +727,16 @@ npc_set_ipv6ext_ltype_mask(struct npc_parse_state *pst)
>          * because for AH and ESP, LC LFLAG is zero and we don't want to match
>          * zero in LFLAG.
>          */
> -       lcflag_offset =
> -               __builtin_popcount(pst->npc->keyx_supp_nmask[pst->nix_intf] &
> -                                  ((1ULL << NPC_LFLAG_LC_OFFSET) - 1));
> -       lcflag_offset *= 4;
> -
> -       mask = (0xfULL << lcflag_offset);
> -       val = pst->flow->mcam_data[0] & mask;
> -       if (val)
> -               pst->flow->mcam_mask[0] |= mask;
> +       if (pst->npc->keyx_supp_nmask[pst->nix_intf] & (1ULL << NPC_LFLAG_LC_OFFSET)) {
> +               lcflag_offset = __builtin_popcount(pst->npc->keyx_supp_nmask[pst->nix_intf] &
> +                                                  ((1ULL << NPC_LFLAG_LC_OFFSET) - 1));
> +               lcflag_offset *= 4;
> +
> +               mask = (0xfULL << lcflag_offset);
> +               val = pst->flow->mcam_data[0] & mask;
> +               if (val)
> +                       pst->flow->mcam_mask[0] |= mask;
> +       }
>  }
>
>  int
> --
> 2.35.3
>

      reply	other threads:[~2023-01-12 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  6:36 psatheesh
2023-01-12 13:32 ` Jerin Jacob [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=CALBAE1Mo2ExiAGc8yrF9zerzt_TZsCWdxRWmmZB1uG8eM6_-8Q@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stable@dpdk.org \
    /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).