DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>, Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@mellanox.com>,
	Dekel Peled <dekelp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/3] net/mlx5: update MPLS item support
Date: Thu, 15 Nov 2018 20:44:37 +0000	[thread overview]
Message-ID: <DB7PR05MB44265886937327B64BE29194C3DC0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1542295034-16098-1-git-send-email-dekelp@mellanox.com>

Thursday, November 15, 2018 5:17 PM, Dekel Peled:
> Subject: [dpdk-dev] [PATCH v3 0/3] net/mlx5: update MPLS item support
> 
> This series updates support of MPLS item, in verbs flow engine and in Direct
> Verbs flow engine.
> Patch 1/3 adds support of MPLS item in DV flow engine.
> Patch 2/3 updates the MPLS item validation in both flow engines.
> Patch 3/3 fixes tunnel ptype of MPLS in UDP.
> 

Series applied w/ the following changes (please shout if you disagree):
1. change first commit singed-of and author to you. You did most of the work there 😊.
2. removed the HAVE_IBV_DEVICE_MPLS_SUPPORT ifdef from the dv code. Looks like this flag has nothing todo with the compilation of the related code. 


> ---
> v3:
> - Add patch 3/3 to series.
> - Update patch 1/3 to set data in matcher and key at corect address.
> - Update patch 2/3 to validate mpls_en is set in device configuration.
> v2:
> - Add patch 1/2 to series.
> - Update patch 2/2 to correctly validate MPLS item.
> ---
> 
> Dekel Peled (2):
>   net/mlx5: fix MPLS item validation
>   net/mlx5: fix tunnel ptype of MPLS in UDP
> 
> Shahaf Shuler (1):
>   net/mlx5: add MPLS to Direct Verbs flow engine
> 
>  drivers/net/mlx5/mlx5_flow.c       |  25 ++++--
>  drivers/net/mlx5/mlx5_flow.h       |   8 +-
>  drivers/net/mlx5/mlx5_flow_dv.c    | 179
> +++++++++++++++++++++++++++++--------
>  drivers/net/mlx5/mlx5_flow_verbs.c |  44 ++++-----
>  4 files changed, 192 insertions(+), 64 deletions(-)
> 
> --
> 1.8.3.1


  reply	other threads:[~2018-11-15 20:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  9:20 [dpdk-dev] [PATCH] net/mlx5: fix MPLS item validation Dekel Peled
2018-11-12  9:52 ` Ori Kam
2018-11-13  9:51 ` [dpdk-dev] [PATCH v2 0/2] net/mlx5: update MPLS item support Dekel Peled
2018-11-15 15:17   ` [dpdk-dev] [PATCH v3 0/3] " Dekel Peled
2018-11-15 20:44     ` Shahaf Shuler [this message]
2018-11-15 15:17   ` [dpdk-dev] [PATCH v3 1/3] net/mlx5: add MPLS to Direct Verbs flow engine Dekel Peled
2018-11-15 15:17   ` [dpdk-dev] [PATCH v3 2/3] net/mlx5: fix MPLS item validation Dekel Peled
2018-11-15 15:17   ` [dpdk-dev] [PATCH v3 3/3] net/mlx5: fix tunnel ptype of MPLS in UDP Dekel Peled
2018-11-13  9:51 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: add MPLS to Direct Verbs flow engine Dekel Peled
2018-11-13  9:51 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix MPLS item validation Dekel Peled

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=DB7PR05MB44265886937327B64BE29194C3DC0@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=yskoh@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).