From: Jakub Kicinski <kuba@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: Boris Pismenny <borisp@nvidia.com>,
John Fastabend <john.fastabend@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>, Gal Pressman <gal@nvidia.com>,
Maxim Mikityanskiy <maximmi@nvidia.com>
Subject: Re: [PATCH net-next V3 2/6] net/tls: Multi-threaded calls to TX tls_dev_del
Date: Thu, 28 Jul 2022 21:56:13 -0700 [thread overview]
Message-ID: <20220728215613.3dfa0ac9@kernel.org> (raw)
In-Reply-To: <20220727094346.10540-3-tariqt@nvidia.com>
On Wed, 27 Jul 2022 12:43:42 +0300 Tariq Toukan wrote:
> + flush_workqueue(destruct_wq);
> + destroy_workqueue(destruct_wq);
IIRC destroy does a flush internally, please follow up.
next prev parent reply other threads:[~2022-07-29 4:56 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 [this message]
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 ` [PATCH net-next V3 0/6] mlx5e use TLS TX pool to improve connection rate 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=20220728215613.3dfa0ac9@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=maximmi@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).