[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0794d1e7-7402-d41b-3d0d-7ff159645bf7@suse.de>
Date: Wed, 10 May 2023 01:07:06 +0200
From: Hannes Reinecke <hare@...e.de>
To: Max Gurtovoy <mgurtovoy@...dia.com>, Jakub Kicinski <kuba@...nel.org>
Cc: 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 5/10/23 01:02, Max Gurtovoy wrote:
>
>
> On 09/05/2023 18:13, Jakub Kicinski wrote:
>> 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.
>
> how come it will bail out only for NVMe/TLS and not for Other_user/TLS ?
>
Oh, it will bail for other TLS users as well.
Point is it will not bail for _non_ TLS connections, causing the issue.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
Powered by blists - more mailing lists