From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, soheil@google.com, weiwan@google.com,
shakeelb@google.com, ncardwell@google.com, edumazet@google.com
Subject: Re: [PATCH net-next 0/7] net: reduce tcp_memory_allocated inflation
Date: Sat, 11 Jun 2022 00:10:14 +0000 [thread overview]
Message-ID: <165490621420.10458.10325984202458401848.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220609063412.2205738-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Jun 2022 23:34:05 -0700 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Hosts with a lot of sockets tend to hit so called TCP memory pressure,
> leading to very bad TCP performance and/or OOM.
>
> The problem is that some TCP sockets can hold up to 2MB of 'forward
> allocations' in their per-socket cache (sk->sk_forward_alloc),
> and there is no mechanism to make them relinquish their share
> under mem pressure.
> Only under some potentially rare events their share is reclaimed,
> one socket at a time.
>
> [...]
Here is the summary with links:
- [net-next,1/7] Revert "net: set SK_MEM_QUANTUM to 4096"
https://git.kernel.org/netdev/net-next/c/e70f3c701276
- [net-next,2/7] net: remove SK_MEM_QUANTUM and SK_MEM_QUANTUM_SHIFT
https://git.kernel.org/netdev/net-next/c/100fdd1faf50
- [net-next,3/7] net: add per_cpu_fw_alloc field to struct proto
https://git.kernel.org/netdev/net-next/c/0defbb0af775
- [net-next,4/7] net: implement per-cpu reserves for memory_allocated
https://git.kernel.org/netdev/net-next/c/3cd3399dd7a8
- [net-next,5/7] net: fix sk_wmem_schedule() and sk_rmem_schedule() errors
https://git.kernel.org/netdev/net-next/c/7c80b038d23e
- [net-next,6/7] net: keep sk->sk_forward_alloc as small as possible
https://git.kernel.org/netdev/net-next/c/4890b686f408
- [net-next,7/7] net: unexport __sk_mem_{raise|reduce}_allocated
https://git.kernel.org/netdev/net-next/c/0f2c2693988a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-06-11 0:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 6:34 [PATCH net-next 0/7] net: reduce tcp_memory_allocated inflation Eric Dumazet
2022-06-09 6:34 ` [PATCH net-next 1/7] Revert "net: set SK_MEM_QUANTUM to 4096" Eric Dumazet
2022-06-09 15:08 ` Shakeel Butt
2022-06-09 6:34 ` [PATCH net-next 2/7] net: remove SK_MEM_QUANTUM and SK_MEM_QUANTUM_SHIFT Eric Dumazet
2022-06-09 15:09 ` Shakeel Butt
2022-06-09 6:34 ` [PATCH net-next 3/7] net: add per_cpu_fw_alloc field to struct proto Eric Dumazet
2022-06-09 15:11 ` Shakeel Butt
2022-06-09 6:34 ` [PATCH net-next 4/7] net: implement per-cpu reserves for memory_allocated Eric Dumazet
2022-06-09 13:33 ` Soheil Hassas Yeganeh
2022-06-09 13:47 ` Eric Dumazet
2022-06-09 13:48 ` Soheil Hassas Yeganeh
2022-06-09 14:46 ` Neal Cardwell
2022-06-09 15:07 ` Shakeel Butt
2022-06-09 15:09 ` Neal Cardwell
2022-06-09 15:43 ` Eric Dumazet
2022-06-09 15:12 ` Shakeel Butt
2022-06-09 6:34 ` [PATCH net-next 5/7] net: fix sk_wmem_schedule() and sk_rmem_schedule() errors Eric Dumazet
2022-06-09 15:18 ` Shakeel Butt
2022-06-09 6:34 ` [PATCH net-next 6/7] net: keep sk->sk_forward_alloc as small as possible Eric Dumazet
2022-06-09 16:38 ` Shakeel Butt
2022-06-10 23:00 ` Mat Martineau
2022-10-13 13:15 ` K Prateek Nayak
2022-10-13 14:35 ` Eric Dumazet
2022-10-13 15:52 ` Shakeel Butt
2022-10-14 8:32 ` K Prateek Nayak
2022-10-14 8:30 ` K Prateek Nayak
2022-10-15 20:19 ` Eric Dumazet
2022-10-17 4:04 ` K Prateek Nayak
2022-06-09 6:34 ` [PATCH net-next 7/7] net: unexport __sk_mem_{raise|reduce}_allocated Eric Dumazet
2022-06-09 16:38 ` Shakeel Butt
2022-06-09 13:33 ` [PATCH net-next 0/7] net: reduce tcp_memory_allocated inflation Soheil Hassas Yeganeh
2022-06-11 0:10 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165490621420.10458.10325984202458401848.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shakeelb@google.com \
--cc=soheil@google.com \
--cc=weiwan@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).