netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>,
	"Saeed Mahameed" <saeedm@nvidia.com>
Subject: [pull request][net-next 0/4] mlx5 updates 2020-10-12
Date: Mon, 12 Oct 2020 15:41:48 -0700	[thread overview]
Message-ID: <20201012224152.191479-1-saeedm@nvidia.com> (raw)

Hi Jakub,

This small series add xfrm IPSec TX offload support to mlx5 driver.

Please pull and let me know if there is any problem.

Thanks,
Saeed.

---
The following changes since commit 547848af58e3eb5a0d8b0a5e6433042f111788e2:

  Merge branch 'bnxt_en-Updates-for-net-next' (2020-10-12 14:42:55 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-updates-2020-10-12

for you to fetch changes up to 5be019040cb7bab4caf152cacadffee91a78b506:

  net/mlx5e: IPsec: Add Connect-X IPsec Tx data path offload (2020-10-12 15:37:45 -0700)

----------------------------------------------------------------
mlx5-updates-2020-10-12

Updates to mlx5 driver:
- Cleanup fix of uininitialized pointer read
- xfrm IPSec TX offload

----------------------------------------------------------------
Colin Ian King (1):
      net/mlx5: Fix uininitialized pointer read on pointer attr

Huy Nguyen (2):
      net/mlx5: Add NIC TX domain namespace
      net/mlx5e: IPsec: Add TX steering rule per IPsec state

Raed Salem (1):
      net/mlx5e: IPsec: Add Connect-X IPsec Tx data path offload

 drivers/net/ethernet/mellanox/mlx5/core/en/fs.h    |   1 +
 .../mellanox/mlx5/core/en_accel/en_accel.h         |  46 +++++-
 .../ethernet/mellanox/mlx5/core/en_accel/ipsec.c   |   3 +
 .../ethernet/mellanox/mlx5/core/en_accel/ipsec.h   |   2 +
 .../mellanox/mlx5/core/en_accel/ipsec_fs.c         | 178 ++++++++++++++++++++-
 .../mellanox/mlx5/core/en_accel/ipsec_rxtx.c       | 110 +++++++++++--
 .../mellanox/mlx5/core/en_accel/ipsec_rxtx.h       |  29 +++-
 drivers/net/ethernet/mellanox/mlx5/core/en_tc.c    |   1 -
 drivers/net/ethernet/mellanox/mlx5/core/en_tx.c    |  43 ++++-
 drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c   |   3 +
 drivers/net/ethernet/mellanox/mlx5/core/fs_core.c  |  19 ++-
 include/linux/mlx5/fs.h                            |   1 +
 include/linux/mlx5/qp.h                            |   6 +-
 13 files changed, 406 insertions(+), 36 deletions(-)

             reply	other threads:[~2020-10-12 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 22:41 Saeed Mahameed [this message]
2020-10-12 22:41 ` [net-next 1/4] net/mlx5: Fix uininitialized pointer read on pointer attr Saeed Mahameed
2020-10-12 22:41 ` [net-next 2/4] net/mlx5: Add NIC TX domain namespace Saeed Mahameed
2020-10-12 22:41 ` [net-next 3/4] net/mlx5e: IPsec: Add TX steering rule per IPsec state Saeed Mahameed
2020-10-12 22:41 ` [net-next 4/4] net/mlx5e: IPsec: Add Connect-X IPsec Tx data path offload Saeed Mahameed
2020-10-14  3:03 ` [pull request][net-next 0/4] mlx5 updates 2020-10-12 Jakub Kicinski

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=20201012224152.191479-1-saeedm@nvidia.com \
    --to=saeedm@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).