netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gal Pressman <gal@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, Saeed Mahameed <saeedm@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>,
	John Fastabend <john.fastabend@gmail.com>,
	"Boris Pismenny" <borisp@nvidia.com>,
	Gal Pressman <gal@nvidia.com>
Subject: [PATCH net-next v2 0/4] Support 256 bit TLS keys with device offload
Date: Tue, 20 Sep 2022 16:01:46 +0300	[thread overview]
Message-ID: <20220920130150.3546-1-gal@nvidia.com> (raw)

Hey,
This series adds support for 256 bit TLS keys with device offload, and a
cleanup patch to remove repeating code:
- Patches #1-2 add cipher sizes descriptors which allow reducing the
  amount of code duplications.
- Patch #3 allows 256 bit keys to be TX offloaded in the tls module (RX
  already supported).
- Patch #4 adds 256 bit keys support to the mlx5 driver.

Changelog -
v1->v2: https://lore.kernel.org/all/20220914090520.4170-1-gal@nvidia.com/
* Add a missing '=' in initializer
* Add missing unlocks in resync_handle_seq_match()

Thanks,
Gal

Gal Pressman (3):
  net/tls: Use cipher sizes structs
  net/tls: Support 256 bit keys with TX device offload
  net/mlx5e: Support 256 bit keys with kTLS device offload

Tariq Toukan (1):
  net/tls: Describe ciphers sizes by const structs

 .../mellanox/mlx5/core/en_accel/ktls.h        |  7 +-
 .../mellanox/mlx5/core/en_accel/ktls_rx.c     | 45 +++++++++--
 .../mellanox/mlx5/core/en_accel/ktls_tx.c     | 41 ++++++++--
 .../mellanox/mlx5/core/en_accel/ktls_txrx.c   | 27 ++++++-
 .../mellanox/mlx5/core/en_accel/ktls_utils.h  |  8 +-
 include/net/tls.h                             | 10 +++
 net/tls/tls_device.c                          | 61 ++++++++------
 net/tls/tls_device_fallback.c                 | 79 +++++++++++++------
 net/tls/tls_main.c                            | 17 ++++
 9 files changed, 227 insertions(+), 68 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-09-20 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 13:01 Gal Pressman [this message]
2022-09-20 13:01 ` [PATCH net-next v2 1/4] net/tls: Describe ciphers sizes by const structs Gal Pressman
2022-09-20 13:01 ` [PATCH net-next v2 2/4] net/tls: Use cipher sizes structs Gal Pressman
2022-09-20 13:01 ` [PATCH net-next v2 3/4] net/tls: Support 256 bit keys with TX device offload Gal Pressman
2022-09-20 13:01 ` [PATCH net-next v2 4/4] net/mlx5e: Support 256 bit keys with kTLS " Gal Pressman
2022-09-23  0:40 ` [PATCH net-next v2 0/4] Support 256 bit TLS keys with " patchwork-bot+netdevbpf

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=20220920130150.3546-1-gal@nvidia.com \
    --to=gal@nvidia.com \
    --cc=borisp@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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).