linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	ncardwell@google.com, pabeni@redhat.com, willemb@google.com,
	matttbe@kernel.org, martineau@kernel.org, hannes@cmpxchg.org,
	mhocko@kernel.org, roman.gushchin@linux.dev,
	shakeel.butt@linux.dev, akpm@linux-foundation.org,
	mkoutny@suse.com, tj@kernel.org, horms@kernel.org,
	geliang@kernel.org, muchun.song@linux.dev,
	almasrymina@google.com, kuni1840@gmail.com,
	netdev@vger.kernel.org, mptcp@lists.linux.dev,
	cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v5 net-next 00/10] net-memcg: Gather memcg code under CONFIG_MEMCG.
Date: Wed, 20 Aug 2025 15:00:23 +0000	[thread overview]
Message-ID: <175570202351.267477.6309911387508861679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250815201712.1745332-1-kuniyu@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 15 Aug 2025 20:16:08 +0000 you wrote:
> This series converts most sk->sk_memcg access to helper functions
> under CONFIG_MEMCG and finally defines sk_memcg under CONFIG_MEMCG.
> 
> This is v5 of the series linked below but without core changes
> that decoupled memcg and global socket memory accounting.
> 
> I will defer the changes to a follow-up series that will use BPF
> to store a flag in sk->sk_memcg.
> 
> [...]

Here is the summary with links:
  - [v5,net-next,01/10] mptcp: Fix up subflow's memcg when CONFIG_SOCK_CGROUP_DATA=n.
    https://git.kernel.org/netdev/net-next/c/68889dfd547b
  - [v5,net-next,02/10] mptcp: Use tcp_under_memory_pressure() in mptcp_epollin_ready().
    https://git.kernel.org/netdev/net-next/c/1068b48ed108
  - [v5,net-next,03/10] tcp: Simplify error path in inet_csk_accept().
    https://git.kernel.org/netdev/net-next/c/e2afa83296bb
  - [v5,net-next,04/10] net: Call trace_sock_exceed_buf_limit() for memcg failure with SK_MEM_RECV.
    https://git.kernel.org/netdev/net-next/c/9d85c565a7b7
  - [v5,net-next,05/10] net: Clean up __sk_mem_raise_allocated().
    https://git.kernel.org/netdev/net-next/c/bd4aa2337374
  - [v5,net-next,06/10] net-memcg: Introduce mem_cgroup_from_sk().
    https://git.kernel.org/netdev/net-next/c/f7161b234f2e
  - [v5,net-next,07/10] net-memcg: Introduce mem_cgroup_sk_enabled().
    https://git.kernel.org/netdev/net-next/c/43049b0db038
  - [v5,net-next,08/10] net-memcg: Pass struct sock to mem_cgroup_sk_(un)?charge().
    https://git.kernel.org/netdev/net-next/c/bb178c6bc085
  - [v5,net-next,09/10] net-memcg: Pass struct sock to mem_cgroup_sk_under_memory_pressure().
    https://git.kernel.org/netdev/net-next/c/b2ffd10cddde
  - [v5,net-next,10/10] net: Define sk_memcg under CONFIG_MEMCG.
    https://git.kernel.org/netdev/net-next/c/bf64002c94fc

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




      parent reply	other threads:[~2025-08-20 15:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 20:16 Kuniyuki Iwashima
2025-08-15 20:16 ` [PATCH v5 net-next 01/10] mptcp: Fix up subflow's memcg when CONFIG_SOCK_CGROUP_DATA=n Kuniyuki Iwashima
2025-08-15 23:31   ` Shakeel Butt
2025-08-15 20:16 ` [PATCH v5 net-next 02/10] mptcp: Use tcp_under_memory_pressure() in mptcp_epollin_ready() Kuniyuki Iwashima
2025-08-15 23:32   ` Shakeel Butt
2025-08-15 20:16 ` [PATCH v5 net-next 03/10] tcp: Simplify error path in inet_csk_accept() Kuniyuki Iwashima
2025-08-15 23:35   ` Shakeel Butt
2025-08-15 20:16 ` [PATCH v5 net-next 04/10] net: Call trace_sock_exceed_buf_limit() for memcg failure with SK_MEM_RECV Kuniyuki Iwashima
2025-08-15 23:49   ` Shakeel Butt
2025-08-15 20:16 ` [PATCH v5 net-next 05/10] net: Clean up __sk_mem_raise_allocated() Kuniyuki Iwashima
2025-08-15 23:52   ` Shakeel Butt
2025-08-15 20:16 ` [PATCH v5 net-next 06/10] net-memcg: Introduce mem_cgroup_from_sk() Kuniyuki Iwashima
2025-08-15 20:16 ` [PATCH v5 net-next 07/10] net-memcg: Introduce mem_cgroup_sk_enabled() Kuniyuki Iwashima
2025-08-15 20:16 ` [PATCH v5 net-next 08/10] net-memcg: Pass struct sock to mem_cgroup_sk_(un)?charge() Kuniyuki Iwashima
2025-08-15 20:16 ` [PATCH v5 net-next 09/10] net-memcg: Pass struct sock to mem_cgroup_sk_under_memory_pressure() Kuniyuki Iwashima
2025-08-20  1:23   ` Jakub Kicinski
2025-08-20  1:28     ` Shakeel Butt
2025-08-15 20:16 ` [PATCH v5 net-next 10/10] net: Define sk_memcg under CONFIG_MEMCG Kuniyuki Iwashima
2025-08-20 15:00 ` 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=175570202351.267477.6309911387508861679.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=almasrymina@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=linux-mm@kvack.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mkoutny@suse.com \
    --cc=mptcp@lists.linux.dev \
    --cc=muchun.song@linux.dev \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=tj@kernel.org \
    --cc=willemb@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