[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a5b742c7530226af4fc7cdf67269be9d3aa842c2.camel@wdc.com>
Date: Thu, 4 Sep 2025 23:41:53 +0000
From: Wilfred Mallawa <wilfred.mallawa@....com>
To: "kuba@...nel.org" <kuba@...nel.org>
CC: "corbet@....net" <corbet@....net>, "dlemoal@...nel.org"
<dlemoal@...nel.org>, "davem@...emloft.net" <davem@...emloft.net>, Alistair
Francis <Alistair.Francis@....com>, "john.fastabend@...il.com"
<john.fastabend@...il.com>, "sd@...asysnail.net" <sd@...asysnail.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, "horms@...nel.org"
<horms@...nel.org>, "edumazet@...gle.com" <edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>
Subject: Re: [PATCH v3] net/tls: support maximum record size limit
On Wed, 2025-09-03 at 15:51 -0700, Jakub Kicinski wrote:
> On Wed, 3 Sep 2025 11:47:57 +1000 Wilfred Mallawa wrote:
> > Upcoming Western Digital NVMe-TCP hardware controllers implement
> > TLS
> > support. For these devices, supporting TLS record size negotiation
> > is
> > necessary because the maximum TLS record size supported by the
> > controller
> > is less than the default 16KB currently used by the kernel.
>
> Just to be clear -- the device does not require that the records
> align
> with TCP segments, right?
Yeah, that's correct. There is no requirement for alignment of TLS
records with TCP segments.
Cheers,
Wilfred
Powered by blists - more mailing lists