DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: dev@dpdk.org
Cc: Yongseok Koh <yskoh@mellanox.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: [dpdk-dev] [PATCH v1 0/7] net/mlx5: IPsec offload support
Date: Thu, 23 Nov 2017 17:13:02 +0100	[thread overview]
Message-ID: <cover.1511453340.git.nelio.laranjeiro@6wind.com> (raw)

Add support for IPsec using rte_security on ConnectX-4 Lx INNOVA NIC.

This support is still in progress on all side (RDMA-Core and Linux Kernel) it
is only enable at compilation time when the expected symbols are present in
Verbs, even in such situation static assert are present to assure the offload
request can be understood by the NIC (those values may change once patches in
RDMA-Core are up-streamed).

Minor changes expected in v2:

 - Rebased on top of new offload API.
 - Eventual modifications to match upstream RDMA-Core and Linux Kernel
 - RSS on SPI.
 - ESN support.
 - Documentation update to explain how to use the INNOVA NIC.

Applies on top of:

 http://dpdk.org/dev/patchwork/patch/31592/

Aviad Yehezkel (2):
  net/mlx5: add IPsec Tx/Rx offload support
  net/mlx5: add security capability function

Nelio Laranjeiro (4):
  net: define Mellanox ether type for embed metadata
  net/mlx5: handle the IPsec support from Verbs
  net/mlx5: simplify error handling in flow action parsing
  net/mlx5: add device parameter to enabled IPsec

Shahaf Shuler (1):
  net/mlx5: support security flow action

 doc/guides/nics/mlx5.rst       |   9 +
 drivers/net/mlx5/Makefile      |   6 +
 drivers/net/mlx5/mlx5.c        |  52 ++++++
 drivers/net/mlx5/mlx5.h        |  10 ++
 drivers/net/mlx5/mlx5_ethdev.c |   4 +
 drivers/net/mlx5/mlx5_flow.c   | 395 +++++++++++++++++++++++++++++++++--------
 drivers/net/mlx5/mlx5_ipsec.c  | 318 +++++++++++++++++++++++++++++++++
 drivers/net/mlx5/mlx5_prm.h    |  39 ++++
 drivers/net/mlx5/mlx5_rxtx.c   | 104 ++++++++++-
 drivers/net/mlx5/mlx5_rxtx.h   |   4 +-
 drivers/net/mlx5/mlx5_txq.c    |   1 +
 lib/librte_net/rte_ether.h     |   2 +
 12 files changed, 861 insertions(+), 83 deletions(-)
 create mode 100644 drivers/net/mlx5/mlx5_ipsec.c

-- 
2.11.0

             reply	other threads:[~2017-11-23 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 16:13 Nelio Laranjeiro [this message]
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 1/7] net: define Mellanox ether type for embed metadata Nelio Laranjeiro
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 2/7] net/mlx5: handle the IPsec support from Verbs Nelio Laranjeiro
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 3/7] net/mlx5: add IPsec Tx/Rx offload support Nelio Laranjeiro
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 4/7] net/mlx5: add security capability function Nelio Laranjeiro
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 5/7] net/mlx5: simplify error handling in flow action parsing Nelio Laranjeiro
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 6/7] net/mlx5: support security flow action Nelio Laranjeiro
2017-11-23 16:13 ` [dpdk-dev] [PATCH v1 7/7] net/mlx5: add device parameter to enabled IPsec 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.1511453340.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).