DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Suanming Mou <suanmingm@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@mellanox.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/mlx5: fix header modifiy choose wrong layer type
Date: Wed, 19 Feb 2020 15:31:57 +0000	[thread overview]
Message-ID: <AM0PR0502MB40194CD2BB34D37866188FA7D2100@AM0PR0502MB4019.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1582122380-54467-3-git-send-email-suanmingm@mellanox.com>



From: Suanming Mou
> Currently, for header modify actions after tunnel decapsulation, the header
> modify actions will still select the old outermost layer type.
> It will cause header modify actions get the wrong layer type.
> 
> Add the tunnel decap flag to indicate the layer type to get for header modify
> actions.
> 
> Fixes: 4bb14c83df95 ("net/mlx5: support modify header using Direct Verbs")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Suanming Mou <suanmingm@mellanox.com>
Acked-by: Matan Azrad <matan@mellanox.com>

  reply	other threads:[~2020-02-19 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 14:26 [dpdk-dev] [PATCH 0/2] net/mlx5: fix incorrect layer choose with decap Suanming Mou
2020-02-19 14:26 ` [dpdk-dev] [PATCH 1/2] net/mlx5: fix wrong layer validation with decapsulation Suanming Mou
2020-02-19 15:31   ` Matan Azrad
2020-02-19 14:26 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix header modifiy choose wrong layer type Suanming Mou
2020-02-19 15:31   ` Matan Azrad [this message]
2020-02-20 11:26 ` [dpdk-dev] [PATCH 0/2] net/mlx5: fix incorrect layer choose with decap Raslan Darawsheh

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=AM0PR0502MB40194CD2BB34D37866188FA7D2100@AM0PR0502MB4019.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=rasland@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@mellanox.com \
    --cc=viacheslavo@mellanox.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).