Re: [PATCH net-next 17/20] tcp: defer skb freeing after socket lock is released
From: Jakub Kicinski <kuba@kernel.org> Date: 2021-11-16 14:27:39
On Mon, 15 Nov 2021 11:02:46 -0800 Eric Dumazet wrote:
One cpu can now be fully utilized for the kernel->user copy,
and another cpu is handling BH processing and skb/page
allocs/frees (assuming RFS is not forcing use of a single CPU)
Are you saying the kernel->user copy is not under the socket lock
today? I'm working on getting the crypto & copy from under the socket
lock for ktls, and it looked like tcp does the copy under the lock.