DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dekel Peled <dekelp@mellanox.com>
To: matan@mellanox.com, viacheslavo@mellanox.com
Cc: rasland@mellanox.com, orika@mellanox.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH 00/11] net/mlx5: vlan actions validation fixes
Date: Wed, 22 Jan 2020 16:27:12 +0200	[thread overview]
Message-ID: <cover.1579703134.git.dekelp@mellanox.com> (raw)

This series includes several patches, fixing different faults in
validation functions of VLAN actions.

Series-acked-by: Ori Kam <orika@mellanox.com>

Dekel Peled (11):
  net/mlx5: fix masks of encap and decap actions
  net/mlx5: fix invalid check for VLAN actions
  net/mlx5: fix bit mask used for push VLAN validate
  net/mlx5: fix allow push VLAN without VID value
  net/mlx5: unify validation of drop action
  net/mlx5: fix block push VLAN action on Rx
  net/mlx5: fix block pop VLAN action on Tx
  net/mlx5: fix pop VLAN action validation function
  net/mlx5: fix the set VLAN VID action validation
  net/mlx5: update description of validation funcs
  doc: update MLX5 supported hardware offloads table

 doc/guides/nics/mlx5.rst           |   8 +--
 drivers/net/mlx5/mlx5_flow.c       |  25 +------
 drivers/net/mlx5/mlx5_flow.h       |   6 +-
 drivers/net/mlx5/mlx5_flow_dv.c    | 139 +++++++++++++------------------------
 drivers/net/mlx5/mlx5_flow_verbs.c |  12 ++++
 5 files changed, 65 insertions(+), 125 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-01-22 14:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 14:27 Dekel Peled [this message]
2020-01-22 14:27 ` [dpdk-dev] [PATCH 01/11] net/mlx5: fix masks of encap and decap actions Dekel Peled
2020-01-23  7:56   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 02/11] net/mlx5: fix invalid check for VLAN actions Dekel Peled
2020-01-23  7:56   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 03/11] net/mlx5: fix bit mask used for push VLAN validate Dekel Peled
2020-01-23  7:56   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 04/11] net/mlx5: fix allow push VLAN without VID value Dekel Peled
2020-01-23  7:57   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 05/11] net/mlx5: unify validation of drop action Dekel Peled
2020-01-23  7:57   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 06/11] net/mlx5: fix block push VLAN action on Rx Dekel Peled
2020-01-23  7:57   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 07/11] net/mlx5: fix block pop VLAN action on Tx Dekel Peled
2020-01-23  7:57   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 08/11] net/mlx5: fix pop VLAN action validation function Dekel Peled
2020-01-23  7:57   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 09/11] net/mlx5: fix the set VLAN VID action validation Dekel Peled
2020-01-23  7:58   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 10/11] net/mlx5: update description of validation funcs Dekel Peled
2020-01-23  7:58   ` Slava Ovsiienko
2020-01-22 14:27 ` [dpdk-dev] [PATCH 11/11] doc: update MLX5 supported hardware offloads table Dekel Peled
2020-01-23  7:58   ` Slava Ovsiienko
2020-01-26 15:48 ` [dpdk-dev] [PATCH 00/11] net/mlx5: vlan actions validation fixes 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=cover.1579703134.git.dekelp@mellanox.com \
    --to=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=rasland@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).