[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230509081308.4a531d4e@kernel.org>
Date: Tue, 9 May 2023 08:13:08 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Hannes Reinecke <hare@...e.de>
Cc: Max Gurtovoy <mgurtovoy@...dia.com>, Sagi Grimberg <sagi@...mberg.me>,
Christoph Hellwig <hch@....de>, Keith Busch <kbusch@...nel.org>,
linux-nvme@...ts.infradead.org, Chuck Lever <chuck.lever@...cle.com>,
kernel-tls-handshake@...ts.linux.dev, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>
Subject: Re: [PATCH 07/17] net/tls: handle MSG_EOR for tls_sw TX flow
On Tue, 9 May 2023 16:18:30 +0200 Hannes Reinecke wrote:
> > This seems like a nice optimization but seems not mandatory for the
> > acceptance of TLS support in nvme/tcp.
> >
> > I wonder if this can go to net/tls as a standalone patch ?
>
> Errm. Without this NVMe/TLS will not work as sendmsg/sendpage will
> bail out.
> So yes, surely it can be applied as a standalone patch, but that
> only makes sense if it will be applied _before_ the rest of the
> nvme/tls patches.
>
> Not sure how best to coordinate this.
You should apply it on a branch based on -rc1 and then both us and
$appropriate-nvme-maintainer can pull it in.
Powered by blists - more mailing lists