From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, borisp@nvidia.com, john.fastabend@gmail.com,
maximmi@nvidia.com, tariqt@nvidia.com, vfedorenko@novek.ru
Subject: Re: [PATCH net-next v3 0/7] tls: rx: decrypt from the TCP queue
Date: Tue, 26 Jul 2022 22:00:14 +0000 [thread overview]
Message-ID: <165887281481.18038.16801688552848755722.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220722235033.2594446-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 22 Jul 2022 16:50:26 -0700 you wrote:
> This is the final part of my TLS Rx rework. It switches from
> strparser to decrypting data from skbs queued in TCP. We don't
> need the full strparser for TLS, its needs are very basic.
> This set gives us a small but measurable (6%) performance
> improvement (continuous stream).
>
> v2: drop the __exit marking for the unroll path
> v3: drop tcp_recv_skb() in patch 5
>
> [...]
Here is the summary with links:
- [net-next,v3,1/7] tls: rx: wrap recv_pkt accesses in helpers
https://git.kernel.org/netdev/net-next/c/b92a13d488de
- [net-next,v3,2/7] tls: rx: factor SW handling out of tls_rx_one_record()
https://git.kernel.org/netdev/net-next/c/dd47ed3620e6
- [net-next,v3,3/7] tls: rx: don't free the output in case of zero-copy
https://git.kernel.org/netdev/net-next/c/b93f5700164d
- [net-next,v3,4/7] tls: rx: device: keep the zero copy status with offload
https://git.kernel.org/netdev/net-next/c/d4e5db645221
- [net-next,v3,5/7] tcp: allow tls to decrypt directly from the tcp rcv queue
https://git.kernel.org/netdev/net-next/c/3f92a64e44e5
- [net-next,v3,6/7] tls: rx: device: add input CoW helper
https://git.kernel.org/netdev/net-next/c/8b3c59a7a0be
- [net-next,v3,7/7] tls: rx: do not use the standard strparser
https://git.kernel.org/netdev/net-next/c/84c61fe1a75b
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-26 22:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 23:50 [PATCH net-next v3 0/7] tls: rx: decrypt from the TCP queue Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 1/7] tls: rx: wrap recv_pkt accesses in helpers Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 2/7] tls: rx: factor SW handling out of tls_rx_one_record() Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 3/7] tls: rx: don't free the output in case of zero-copy Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 4/7] tls: rx: device: keep the zero copy status with offload Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 5/7] tcp: allow tls to decrypt directly from the tcp rcv queue Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 6/7] tls: rx: device: add input CoW helper Jakub Kicinski
2022-07-22 23:50 ` [PATCH net-next v3 7/7] tls: rx: do not use the standard strparser Jakub Kicinski
2022-07-26 9:27 ` Paolo Abeni
2022-07-26 17:01 ` Jakub Kicinski
2022-07-26 17:26 ` Paolo Abeni
2022-08-02 14:54 ` Tariq Toukan
2022-08-02 15:40 ` Jakub Kicinski
2022-08-04 1:24 ` Jakub Kicinski
2022-08-04 6:13 ` Tariq Toukan
2022-08-04 8:05 ` Tariq Toukan
2022-08-04 15:35 ` Jakub Kicinski
2022-08-07 6:01 ` Tariq Toukan
2022-08-04 15:59 ` Jakub Kicinski
2022-08-07 6:01 ` Tariq Toukan
2022-08-08 5:24 ` Tariq Toukan
2022-08-08 18:24 ` Jakub Kicinski
2022-08-09 8:47 ` Tariq Toukan
2023-03-09 15:15 ` Tariq Toukan
2023-03-09 17:54 ` Jakub Kicinski
2023-03-12 17:59 ` Tariq Toukan
2023-03-13 18:22 ` Jakub Kicinski
2023-03-15 20:26 ` Tariq Toukan
2023-03-16 1:41 ` Jakub Kicinski
2022-07-26 22: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=165887281481.18038.16801688552848755722.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maximmi@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
--cc=vfedorenko@novek.ru \
/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).