From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS
Date: Mon, 3 Jul 2023 12:20:52 +0200 [thread overview]
Message-ID: <e1165086-fd99-ff43-4bca-d39dd1e46cf1@suse.de> (raw)
In-Reply-To: <8fbfa483-caed-870f-68ed-40855feb601f@grimberg.me>
On 7/3/23 12:08, Sagi Grimberg wrote:
>
>
> On 7/3/23 12:04, Hannes Reinecke wrote:
>> Hi all,
>>
>> here are some small fixes to get NVMe-over-TLS up and running.
>> The first three are just minor modifications to have MSG_EOR handled
>> for TLS (and adding a test for it), but the last two implement the
>> ->read_sock() callback for tls_sw and that, I guess, could do with
>> some reviews.
>> It does work with my NVMe-TLS test harness, but what do I know :-)
>
> Hannes, have you tested nvme/tls with the MSG_SPLICE_PAGES series from
> david?
Yes. This patchset has been tested on top of current linus' HEAD, which
includes the MSG_SPLICE_PAGES series (hence the absence of patch hunks
for ->sendpage() and friends).
Cheers,
Hannes
next prev parent reply other threads:[~2023-07-03 10:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 9:04 [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS Hannes Reinecke
2023-07-03 9:04 ` [PATCH 1/5] net/tls: handle MSG_EOR for tls_sw TX flow Hannes Reinecke
2023-07-03 9:04 ` [PATCH 2/5] net/tls: handle MSG_EOR for tls_device " Hannes Reinecke
2023-07-03 9:04 ` [PATCH 3/5] selftests/net/tls: add test for MSG_EOR Hannes Reinecke
2023-07-03 9:04 ` [PATCH 4/5] net/tls: split tls_rx_reader_lock Hannes Reinecke
2023-07-03 10:06 ` Sagi Grimberg
2023-07-03 10:21 ` Hannes Reinecke
2023-07-05 20:55 ` Jakub Kicinski
2023-07-03 9:04 ` [PATCH 5/5] net/tls: implement ->read_sock() Hannes Reinecke
2023-07-04 7:56 ` Paolo Abeni
2023-07-03 10:08 ` [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS Sagi Grimberg
2023-07-03 10:20 ` Hannes Reinecke [this message]
2023-07-03 12:13 ` Hannes Reinecke
2023-07-03 12:19 ` Hannes Reinecke
2023-07-03 12:26 ` David Howells
2023-07-03 12:33 ` Sagi Grimberg
2023-07-03 13:15 ` Hannes Reinecke
2023-07-03 13:42 ` Sagi Grimberg
2023-07-03 13:46 ` Hannes Reinecke
2023-07-03 14:01 ` Sagi Grimberg
2023-07-03 13:57 ` Hannes Reinecke
2023-07-03 14:10 ` Sagi Grimberg
2023-07-03 12:35 ` Hannes Reinecke
2023-07-03 12:45 ` David Howells
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=e1165086-fd99-ff43-4bca-d39dd1e46cf1@suse.de \
--to=hare@suse.de \
--cc=edumazet@google.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sagi@grimberg.me \
/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