patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Jiawei Wang <jiaweiw@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	 Raslan Darawsheh <rasland@nvidia.com>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 19.11] app/testpmd: fix NVGRE encap configuration
Date: Tue, 8 Jun 2021 06:51:25 +0200	[thread overview]
Message-ID: <CAATJJ0+ibUgaRgUqL0MG73M4as=Ntn2ADAeF+GUr3AMcNbh6jQ@mail.gmail.com> (raw)
In-Reply-To: <20210604133733.35056-1-jiaweiw@nvidia.com>

On Fri, Jun 4, 2021 at 3:37 PM Jiawei Wang <jiaweiw@nvidia.com> wrote:
>
> [ upstream commit 9b0da816bdec98c0d6c5d17ccdd337bdbafc3f75 ]
>
> For NVGRE protocol, the default value of 'c_k_s_rsvd0_ver'
> must be 0x2000, and protocol type must be 0x6558 in the NVGRE
> header.
>
> This patch updates these two configurations while parsing the nvgre
> encap.

Thanks, while it is unsure if it will be 19.11.9 or later 19.11.10 it
is applied now.

> Fixes: dcd962fc6b4e ("app/testpmd: add NVGRE encap/decap")
>
> Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
> ---
>  app/test-pmd/cmdline_flow.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
> index da3533c..0b76f7e 100644
> --- a/app/test-pmd/cmdline_flow.c
> +++ b/app/test-pmd/cmdline_flow.c
> @@ -4250,7 +4250,11 @@ static int comp_set_raw_index(struct context *, const struct token *,
>                        .src_addr = nvgre_encap_conf.ipv4_src,
>                        .dst_addr = nvgre_encap_conf.ipv4_dst,
>                 },
> -               .item_nvgre.flow_id = 0,
> +               .item_nvgre = {
> +                       .c_k_s_rsvd0_ver = RTE_BE16(0x2000),
> +                       .protocol = RTE_BE16(RTE_ETHER_TYPE_TEB),
> +                       .flow_id = 0,
> +               },
>         };
>         memcpy(action_nvgre_encap_data->item_eth.dst.addr_bytes,
>                nvgre_encap_conf.eth_dst, RTE_ETHER_ADDR_LEN);
> --
> 1.8.3.1
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

      reply	other threads:[~2021-06-08  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 13:37 Jiawei Wang
2021-06-08  4:51 ` Christian Ehrhardt [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='CAATJJ0+ibUgaRgUqL0MG73M4as=Ntn2ADAeF+GUr3AMcNbh6jQ@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=jiaweiw@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --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).