Linux cgroups development
 help / color / mirror / Atom feed
From: Ridong Chen <ridong.chen@linux.dev>
To: Barry Song <baohua@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Muchun Song <muchun.song@linux.dev>, Chris Li <chrisl@kernel.org>,
	Kairui Song <kasong@tencent.com>,
	David Hildenbrand <david@kernel.org>,
	Yuanchu Xie <yuanchu@google.com>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org, Ridong Chen <chenridong@xiaomi.com>
Subject: Re: [PATCH 1/2] memcg: move mem_cgroup_swappiness to memcontrol.h
Date: Wed, 15 Jul 2026 16:28:04 +0800	[thread overview]
Message-ID: <a28e5f32-6b33-465d-8c62-a155f1f61ca8@linux.dev> (raw)
In-Reply-To: <CAGsJ_4w8P8ERoXJY70wXf71MYEA16vX+JMAaE4sfB4=OqzN_Pg@mail.gmail.com>



On 7/14/2026 9:46 PM, Barry Song wrote:
> On Tue, Jul 14, 2026 at 7:31 PM Ridong Chen <ridong.chen@linux.dev> wrote:
> 
> [...]
>>>>>>
>>>>>> If this is the case, it still seems better to keep
>>>>>> extern int vm_swappiness in include/linux/swap.h.
>>>>>>
>>>>>> Then we don't need the comment:
>>>>>> /* Defined in mm/vmscan.c; used by mem_cgroup_swappiness(). */
>>>>>>
>>>>>> It also makes it clearer that vm_swappiness is an extern variable
>>>>>> belonging to the swap module, rather than the memcontrol module.
>>>>>
>>>>> BTW, if mem_c_group_swappiness() and vm_swappiness are only used
>>>>> within mm/, could all of these be moved to mm/swap.h and
>>>>> mm/internal.h instead?
>>>>>
>>>>> We are making a big effort to move many unrelated things out of
>>>>> include/linux/swap.h recently. Could you check?
>>>>>
>>>>> https://lore.kernel.org/linux-mm/20260708-ch-swap-series-plus-folio-lru-cleanup-v9-0-2bc72b4f8730@gmail.com/
>>>>
>>>> Good suggestion. Moving them to mm/internal.h makes sense. Will update
>>>> in the next version.
>>>
>>> Either mm/swap.h or mm/internal.h.
>>> vm_swappiness probably belongs in mm/swap.h rather than
>>> mm/internal.h, right?
>>>
>>> BTW, I am not particularly eager about this cleanup;
>>> it could be done later as a separate patch.
>>>
>>> If you decide not to do the cleanup, I think it would be better to
>>> leave "extern int vm_swappiness" in include/linux/swap.h rather than
>>> declaring it in include/linux/memcontrol.h?
>> I noticed that some swap-related macros are already defined in
>> mm/internal.h, so I'm planning to place the code right after them for
>> better grouping. Does that work for you?
> 
> We also have mm/swap.h, which is dedicated to exporting
> swap-related things. Is it a better place than mm/internal.h?
> 

Placing it in mm/swap.h is fine with me. Will update.

```
--- a/mm/swap.h
+++ b/mm/swap.h
@@ -4,6 +4,7 @@

  #include <linux/atomic.h> /* for atomic_long_t */
  #include <linux/mm.h> /* for PAGE_SHIFT */
+#include <linux/memcontrol.h>
  struct mempolicy;
  struct swap_iocb;
  struct swap_memcg_table;
@@ -76,6 +77,25 @@ enum swap_cluster_flags {
         CLUSTER_FLAG_MAX,
  };

+extern int vm_swappiness;
+
+static inline int mem_cgroup_swappiness(struct mem_cgroup *memcg)
+{
+#ifdef CONFIG_MEMCG_V1
+       /* Cgroup2 doesn't have per-cgroup swappiness */
+       if (cgroup_subsys_on_dfl(memory_cgrp_subsys))
+               return READ_ONCE(vm_swappiness);
+
+       /* root ? */
+       if (mem_cgroup_disabled() || mem_cgroup_is_root(memcg))
+               return READ_ONCE(vm_swappiness);
+
+       return READ_ONCE(memcg->swappiness);
+#else
+       return READ_ONCE(vm_swappiness);
+#endif
+}
+
```

-- 
Best regards
Ridong


  reply	other threads:[~2026-07-15  8:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  9:11 [PATCH 0/2] mm: fix node reclaim swappiness handling Ridong Chen
2026-07-11  9:11 ` [PATCH 1/2] memcg: move mem_cgroup_swappiness to memcontrol.h Ridong Chen
2026-07-13 15:08   ` Barry Song
2026-07-14  1:19     ` Ridong Chen
2026-07-14  1:43       ` Barry Song
2026-07-14  1:48         ` Barry Song
2026-07-14  7:42           ` Ridong Chen
2026-07-14 10:21             ` Barry Song
2026-07-14 11:31               ` Ridong Chen
2026-07-14 13:46                 ` Barry Song
2026-07-15  8:28                   ` Ridong Chen [this message]
2026-07-11  9:11 ` [PATCH 2/2] mm: vmscan: fix node reclaim ignoring swappiness parameter Ridong Chen
2026-07-13 11:28   ` Johannes Weiner
2026-07-14  7:58     ` Ridong Chen
2026-07-13 15:16   ` Barry Song
2026-07-14  1:10     ` Ridong Chen

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=a28e5f32-6b33-465d-8c62-a155f1f61ca8@linux.dev \
    --to=ridong.chen@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@xiaomi.com \
    --cc=chrisl@kernel.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=yuanchu@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