[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162807840601.323.12461942403559350811.git-patchwork-notify@kernel.org>
Date: Wed, 04 Aug 2021 12:00:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Pavel Tikhomirov <ptikhomirov@...tuozzo.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
arnd@...db.de, edumazet@...gle.com, pabeni@...hat.com,
fw@...len.de, linux-kernel@...r.kernel.org,
linux-alpha@...r.kernel.org, linux-mips@...r.kernel.org,
linux-parisc@...r.kernel.org, sparclinux@...r.kernel.org,
linux-arch@...r.kernel.org, avagin@...il.com, kernel@...nvz.org
Subject: Re: [PATCH v3] sock: allow reading and changing sk_userlocks with
setsockopt
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 4 Aug 2021 10:55:56 +0300 you wrote:
> SOCK_SNDBUF_LOCK and SOCK_RCVBUF_LOCK flags disable automatic socket
> buffers adjustment done by kernel (see tcp_fixup_rcvbuf() and
> tcp_sndbuf_expand()). If we've just created a new socket this adjustment
> is enabled on it, but if one changes the socket buffer size by
> setsockopt(SO_{SND,RCV}BUF*) it becomes disabled.
>
> CRIU needs to call setsockopt(SO_{SND,RCV}BUF*) on each socket on
> restore as it first needs to increase buffer sizes for packet queues
> restore and second it needs to restore back original buffer sizes. So
> after CRIU restore all sockets become non-auto-adjustable, which can
> decrease network performance of restored applications significantly.
>
> [...]
Here is the summary with links:
- [v3] sock: allow reading and changing sk_userlocks with setsockopt
https://git.kernel.org/netdev/net-next/c/04190bf8944d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists