From: patchwork-bot+netdevbpf@kernel•org
To: Tariq Toukan <tariqt@nvidia•com>
Cc: borisp@nvidia•com, john.fastabend@gmail•com, kuba@kernel•org,
davem@davemloft•net, edumazet@google•com, pabeni@redhat•com,
netdev@vger•kernel.org, saeedm@nvidia•com, gal@nvidia•com
Subject: Re: [PATCH net-next V3 0/6] mlx5e use TLS TX pool to improve connection rate
Date: Fri, 29 Jul 2022 05:00:15 +0000 [thread overview]
Message-ID: <165907081590.3346.4921350979287597508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220727094346.10540-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 27 Jul 2022 12:43:40 +0300 you wrote:
> To offload encryption operations, the mlx5 device maintains state and
> keeps track of every kTLS device-offloaded connection. Two HW objects
> are used per TX context of a kTLS offloaded connection: a. Transport
> interface send (TIS) object, to reach the HW context. b. Data Encryption
> Key (DEK) to perform the crypto operations.
>
> These two objects are created and destroyed per TLS TX context, via FW
> commands. In total, 4 FW commands are issued per TLS TX context, which
> seriously limits the connection rate.
>
> [...]
Here is the summary with links:
- [net-next,V3,1/6] net/tls: Perform immediate device ctx cleanup when possible
https://git.kernel.org/netdev/net-next/c/113671b255ee
- [net-next,V3,2/6] net/tls: Multi-threaded calls to TX tls_dev_del
https://git.kernel.org/netdev/net-next/c/7adc91e0c939
- [net-next,V3,3/6] net/mlx5e: kTLS, Introduce TLS-specific create TIS
https://git.kernel.org/netdev/net-next/c/da6682faa82f
- [net-next,V3,4/6] net/mlx5e: kTLS, Take stats out of OOO handler
https://git.kernel.org/netdev/net-next/c/23b1cf1e3fe0
- [net-next,V3,5/6] net/mlx5e: kTLS, Recycle objects of device-offloaded TLS TX connections
https://git.kernel.org/netdev/net-next/c/c4dfe704f53f
- [net-next,V3,6/6] net/mlx5e: kTLS, Dynamically re-size TX recycling pool
https://git.kernel.org/netdev/net-next/c/624bf0992133
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-07-29 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 9:43 [PATCH net-next V3 0/6] mlx5e use TLS TX pool to improve connection rate Tariq Toukan
2022-07-27 9:43 ` [PATCH net-next V3 1/6] net/tls: Perform immediate device ctx cleanup when possible Tariq Toukan
2022-07-27 9:43 ` [PATCH net-next V3 2/6] net/tls: Multi-threaded calls to TX tls_dev_del Tariq Toukan
2022-07-29 4:56 ` Jakub Kicinski
2022-08-01 6:46 ` Tariq Toukan
2022-07-27 9:43 ` [PATCH net-next V3 3/6] net/mlx5e: kTLS, Introduce TLS-specific create TIS Tariq Toukan
2022-07-27 9:43 ` [PATCH net-next V3 4/6] net/mlx5e: kTLS, Take stats out of OOO handler Tariq Toukan
2022-07-27 9:43 ` [PATCH net-next V3 5/6] net/mlx5e: kTLS, Recycle objects of device-offloaded TLS TX connections Tariq Toukan
2022-07-27 9:43 ` [PATCH net-next V3 6/6] net/mlx5e: kTLS, Dynamically re-size TX recycling pool Tariq Toukan
2022-07-29 5:00 ` patchwork-bot+netdevbpf [this message]
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=165907081590.3346.4921350979287597508.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=borisp@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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