DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: dev@dpdk.org, Yongseok Koh <yskoh@mellanox.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: [dpdk-dev] [PATCH v3 0/2] net/mlx5: fix flow director mask
Date: Tue, 17 Apr 2018 11:01:34 +0200	[thread overview]
Message-ID: <cover.1523888984.git.nelio.laranjeiro@6wind.com> (raw)
In-Reply-To: <cover.1523632978.git.nelio.laranjeiro@6wind.com>

Flow director mask as been mistakenly removed from mlx5 PMD.  This series
brings it back.

Changes in v3:

Let flow API handle the mask from the user.

Changes in v2:

Use the L3 structures instead of the l4 in the conversion.

Nelio Laranjeiro (2):
  net/mlx5: split L3/L4 in flow director
  net/mlx5: fix flow director mask

 drivers/net/mlx5/mlx5_flow.c | 164 ++++++++++++++++++-----------------
 1 file changed, 83 insertions(+), 81 deletions(-)

-- 
2.17.0

  reply	other threads:[~2018-04-17  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 14:31 [dpdk-dev] [PATCH " Nelio Laranjeiro
2018-04-12 14:31 ` [dpdk-dev] [PATCH 1/2] net/mlx5: split L3/L4 in flow director Nelio Laranjeiro
2018-04-12 14:31 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix flow director mask Nelio Laranjeiro
2018-04-13 15:28 ` [dpdk-dev] [PATCH v2 0/2] " Nelio Laranjeiro
2018-04-17  9:01   ` Nelio Laranjeiro [this message]
2018-04-23  5:39     ` [dpdk-dev] [PATCH v3 " Shahaf Shuler
2018-04-17  9:01   ` [dpdk-dev] [PATCH v3 1/2] net/mlx5: split L3/L4 in flow director Nelio Laranjeiro
2018-04-17  9:01   ` [dpdk-dev] [PATCH v3 2/2] net/mlx5: fix flow director mask Nelio Laranjeiro
2018-04-13 15:28 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: split L3/L4 in flow director Nelio Laranjeiro
2018-04-13 15:28 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix flow director mask Nelio Laranjeiro

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.1523888984.git.nelio.laranjeiro@6wind.com \
    --to=nelio.laranjeiro@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --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).