From: Shakeel Butt <shakeel.butt@linux.dev>
To: Gregory Price <gourry@gourry.net>
Cc: linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
longman@redhat.com, hannes@cmpxchg.org, mhocko@kernel.org,
roman.gushchin@linux.dev, muchun.song@linux.dev, tj@kernel.org,
mkoutny@suse.com, akpm@linux-foundation.org
Subject: Re: [PATCH v3 2/2] vmscan,cgroup: apply mems_effective to reclaim
Date: Sat, 19 Apr 2025 11:48:45 -0700 [thread overview]
Message-ID: <ro3uqeyri65voutamqttzipfk7yiya4zv5kdiudcmhacrm6tej@br7ebk2kanf4> (raw)
In-Reply-To: <20250419053824.1601470-3-gourry@gourry.net>
On Sat, Apr 19, 2025 at 01:38:24AM -0400, Gregory Price wrote:
>
> +bool cpuset_node_allowed(struct cgroup *cgroup, int nid)
> +{
> + struct cgroup_subsys_state *css;
> + unsigned long flags;
> + struct cpuset *cs;
> + bool allowed;
> +
> + css = cgroup_get_e_css(cgroup, &cpuset_cgrp_subsys);
> + if (!css)
> + return true;
> +
> + cs = container_of(css, struct cpuset, css);
> + spin_lock_irqsave(&callback_lock, flags);
Do we really need callback_lock here? We are not modifying and I am
wondering if simple rcu read lock is enough here (similar to
update_nodemasks_hier() where parent's effective_mems is accessed within
rcu read lock).
> + /* On v1 effective_mems may be empty, simply allow */
> + allowed = node_isset(nid, cs->effective_mems) ||
> + nodes_empty(cs->effective_mems);
> + spin_unlock_irqrestore(&callback_lock, flags);
> + css_put(css);
> + return allowed;
> +}
next prev parent reply other threads:[~2025-04-19 18:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 5:38 [PATCH v3 0/2] vmscan: enforce mems_effective during demotion Gregory Price
2025-04-19 5:38 ` [PATCH v3 1/2] cpuset: rename cpuset_node_allowed to cpuset_current_node_allowed Gregory Price
2025-04-19 18:37 ` Shakeel Butt
2025-04-19 5:38 ` [PATCH v3 2/2] vmscan,cgroup: apply mems_effective to reclaim Gregory Price
2025-04-19 18:48 ` Shakeel Butt [this message]
2025-04-20 0:14 ` Waiman Long
2025-04-21 17:39 ` Shakeel Butt
2025-04-21 22:59 ` Gregory Price
2025-04-21 23:15 ` Shakeel Butt
2025-04-21 23:58 ` Gregory Price
2025-04-22 0:10 ` Shakeel Butt
2025-04-22 0:39 ` Waiman Long
2025-04-22 0:35 ` Waiman Long
2025-04-22 1:00 ` Gregory Price
2025-04-22 0:10 ` Waiman Long
2025-04-22 0:16 ` Shakeel Butt
2025-04-20 0:31 ` Waiman Long
2025-04-20 23:59 ` Gregory Price
2025-04-21 23:37 ` Shakeel Butt
2025-04-19 17:21 ` [PATCH v3 0/2] vmscan: enforce mems_effective during demotion Tejun Heo
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=ro3uqeyri65voutamqttzipfk7yiya4zv5kdiudcmhacrm6tej@br7ebk2kanf4 \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tj@kernel.org \
/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