Thread (5 messages) 5 messages, 2 authors, 2021-09-30

Re: [PATCH v3 net-next 0/3] net: add new socket option SO_RESERVE_MEM

flat view

From: patchwork-bot+netdevbpf@kernel.org
Date: 2021-09-30 12:50:11

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Wed, 29 Sep 2021 10:25:10 -0700 you wrote:
This patch series introduces a new socket option SO_RESERVE_MEM.
This socket option provides a mechanism for users to reserve a certain
amount of memory for the socket to use. When this option is set, kernel
charges the user specified amount of memory to memcg, as well as
sk_forward_alloc. This amount of memory is not reclaimable and is
available in sk_forward_alloc for this socket.
With this socket option set, the networking stack spends less cycles
doing forward alloc and reclaim, which should lead to better system
performance, with the cost of an amount of pre-allocated and
unreclaimable memory, even under memory pressure.
With a tcp_stream test with 10 flows running on a simulated 100ms RTT
link, I can see the cycles spent in __sk_mem_raise_allocated() dropping
by ~0.02%. Not a whole lot, since we already have logic in
sk_mem_uncharge() to only reclaim 1MB when sk_forward_alloc has more
than 2MB free space. But on a system suffering memory pressure
constently, the savings should be more.

[...]
Here is the summary with links:
  - [v3,net-next,1/3] net: add new socket option SO_RESERVE_MEM
    https://git.kernel.org/netdev/net-next/c/2bb2f5fb21b0
  - [v3,net-next,2/3] tcp: adjust sndbuf according to sk_reserved_mem
    https://git.kernel.org/netdev/net-next/c/ca057051cf25
  - [v3,net-next,3/3] tcp: adjust rcv_ssthresh according to sk_reserved_mem
    https://git.kernel.org/netdev/net-next/c/053f368412c9

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help