DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Jack Min <jackmin@mellanox.com>, Raslan Darawsheh <rasland@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix missing ptype for IP-in-IP
Date: Wed, 4 Sep 2019 13:38:35 +0000	[thread overview]
Message-ID: <AM4PR05MB326517520E2824FB429D374DD2B80@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <8b07ad6d289e6b604bfc95f70ded7f78e0cb4489.1565264176.git.jackmin@mellanox.com>

> -----Original Message-----
> From: Xiaoyu Min <jackmin@mellanox.com>
> Sent: Thursday, August 8, 2019 14:39
> To: Shahaf Shuler <shahafs@mellanox.com>; Yongseok Koh
> <yskoh@mellanox.com>; Slava Ovsiienko <viacheslavo@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [PATCH] net/mlx5: fix missing ptype for IP-in-IP
> 
> The hw ptype information is missed for IP-in-IP tunnel.
> It should be RTE_PTYPE_TUNNEL_IP ptype.
> 
> Fixes: 5e33bebdd8d3 ("net/mlx5: support IP-in-IP tunnel")
> 
> Signed-off-by: Xiaoyu Min <jackmin@mellanox.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

> ---
>  drivers/net/mlx5/mlx5_flow.c | 8 ++++++++  drivers/net/mlx5/mlx5_rxtx.h |
> 2 +-
>  2 files changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
> index 9d2c8c9ec5..67a31473d8 100644
> --- a/drivers/net/mlx5/mlx5_flow.c
> +++ b/drivers/net/mlx5/mlx5_flow.c
> @@ -306,6 +306,14 @@ static struct mlx5_flow_tunnel_info tunnels_info[]
> = {
>  		.tunnel = MLX5_FLOW_LAYER_NVGRE,
>  		.ptype = RTE_PTYPE_TUNNEL_NVGRE,
>  	},
> +	{
> +		.tunnel = MLX5_FLOW_LAYER_IPIP,
> +		.ptype = RTE_PTYPE_TUNNEL_IP,
> +	},
> +	{
> +		.tunnel = MLX5_FLOW_LAYER_IPV6_ENCAP,
> +		.ptype = RTE_PTYPE_TUNNEL_IP,
> +	},
>  };
> 
>  /**
> diff --git a/drivers/net/mlx5/mlx5_rxtx.h b/drivers/net/mlx5/mlx5_rxtx.h
> index bad9e9c1f7..4f73d91311 100644
> --- a/drivers/net/mlx5/mlx5_rxtx.h
> +++ b/drivers/net/mlx5/mlx5_rxtx.h
> @@ -40,7 +40,7 @@
>  #include "mlx5_glue.h"
> 
>  /* Support tunnel matching. */
> -#define MLX5_FLOW_TUNNEL 6
> +#define MLX5_FLOW_TUNNEL 8
> 
>  struct mlx5_rxq_stats {
>  #ifdef MLX5_PMD_SOFT_COUNTERS
> --
> 2.21.0


  reply	other threads:[~2019-09-04 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08 11:38 Xiaoyu Min
2019-09-04 13:38 ` Slava Ovsiienko [this message]
2019-09-05  7:52 ` 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=AM4PR05MB326517520E2824FB429D374DD2B80@AM4PR05MB3265.eurprd05.prod.outlook.com \
    --to=viacheslavo@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jackmin@mellanox.com \
    --cc=rasland@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).