From: Matthew Wilcox <willy@infradead.org>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>,
cgroups@vger.kernel.org
Subject: Re: [PATCH] memcg: protect concurrent access to mem_cgroup_idr
Date: Thu, 8 Aug 2024 04:54:57 +0100 [thread overview]
Message-ID: <ZrRBkVu8QrDOBOgs@casper.infradead.org> (raw)
In-Reply-To: <20240802235822.1830976-1-shakeel.butt@linux.dev>
On Fri, Aug 02, 2024 at 04:58:22PM -0700, Shakeel Butt wrote:
> #define MEM_CGROUP_ID_MAX ((1UL << MEM_CGROUP_ID_SHIFT) - 1)
> static DEFINE_IDR(mem_cgroup_idr);
> +static DEFINE_SPINLOCK(memcg_idr_lock);
> +
> +static int mem_cgroup_alloc_id(void)
> +{
> + int ret;
> +
> + idr_preload(GFP_KERNEL);
> + spin_lock(&memcg_idr_lock);
> + ret = idr_alloc(&mem_cgroup_idr, NULL, 1, MEM_CGROUP_ID_MAX + 1,
> + GFP_NOWAIT);
> + spin_unlock(&memcg_idr_lock);
> + idr_preload_end();
> + return ret;
> +}
You know, this works much better as an xarray:
static int mem_cgroup_alloc_id(void)
{
u32 id;
int ret;
ret = xa_alloc(&mem_cgroup_ids, &id, XA_LIMIT(1, MEM_CGROUP_ID_MAX),
GFP_KERNEL);
if (ret < 0)
return ret;
return id;
}
No messing around with preloading, the spinlock is built in and the MAX
works the way you want it to.
next prev parent reply other threads:[~2024-08-08 3:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 23:58 Shakeel Butt
2024-08-05 2:58 ` Muchun Song
2024-08-05 16:59 ` Johannes Weiner
2024-08-05 17:25 ` Roman Gushchin
2024-08-08 3:54 ` Matthew Wilcox [this message]
2024-08-08 5:46 ` Shakeel Butt
2024-08-09 12:23 ` Michal Hocko
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=ZrRBkVu8QrDOBOgs@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.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 \
/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
all inboxes | Powered by JetHome®