Thread (22 messages) 22 messages, 3 authors, 22d ago

Re: [RFC net-next 00/17] MPTCP KTLS support

From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-06-26 16:32:56
Also in: mptcp

On Fri, 26 Jun 2026 15:56:53 +0800 Geliang Tang wrote:
On Mon, 2026-06-22 at 09:00 -0700, Jakub Kicinski wrote:
quoted
On Mon, 22 Jun 2026 18:43:20 +0800 Geliang Tang wrote:  
quoted
Subject: [RFC net-next 00/17] MPTCP KTLS support  
Please no. We have a ton of unfixed bugs and may have to revert some
of
the features we dropped back in. I'd prefer to avoid large new bug
surfaces until we reach an LTS release.  
Sure, I can wait. During this time, I'll go over the implementation
more carefully to make sure there are no issues on the MPTCP side.
The two things that I'd be most interested in understanding better are
1) perf impact on all the pointer chasing and indirect calls you're
   adding
2) what's your plan on implementing HW offload? I understand that _you_
   may not care, but if you follow the ML you'll discover that sooner
   or later some well meaning person will slop code such support.
   We have pretty solid (by kernel standards) documentation for the
   offload. Please read if you haven't already. And then you should
   hopefully realize the huge issue with the layering you chose...
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help