From: Matthew Wilcox <willy@infradead.org>
To: Muchun Song <songmuchun@bytedance.com>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, mhocko@kernel.org,
vdavydov.dev@gmail.com, shakeelb@google.com,
roman.gushchin@linux.dev, shy828301@gmail.com, alexs@kernel.org,
richard.weiyang@gmail.com, david@fromorbit.com,
trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
jaegeuk@kernel.org, chao@kernel.org, kari.argillander@gmail.com,
vbabka@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org, zhengqi.arch@bytedance.com,
duanxiongchun@bytedance.com, fam.zheng@bytedance.com,
smuchun@gmail.com
Subject: Re: [PATCH v6 12/16] mm: list_lru: replace linear array with xarray
Date: Thu, 31 Mar 2022 16:01:45 +0100 [thread overview]
Message-ID: <YkXCWW7ru9Gxyy6G@casper.infradead.org> (raw)
In-Reply-To: <20220228122126.37293-13-songmuchun@bytedance.com>
On Mon, Feb 28, 2022 at 08:21:22PM +0800, Muchun Song wrote:
> @@ -586,27 +508,48 @@ int memcg_list_lru_alloc(struct mem_cgroup *memcg, struct list_lru *lru,
> }
> }
>
> + xas_lock_irqsave(&xas, flags);
> while (i--) {
> + int index = READ_ONCE(table[i].memcg->kmemcg_id);
> struct list_lru_per_memcg *mlru = table[i].mlru;
>
> + xas_set(&xas, index);
> +retry:
> + if (unlikely(index < 0 || xas_error(&xas) || xas_load(&xas))) {
> kfree(mlru);
> + } else {
> + xas_store(&xas, mlru);
> + if (xas_error(&xas) == -ENOMEM) {
> + xas_unlock_irqrestore(&xas, flags);
> + if (xas_nomem(&xas, gfp))
> + xas_set_err(&xas, 0);
> + xas_lock_irqsave(&xas, flags);
> + /*
> + * The xas lock has been released, this memcg
> + * can be reparented before us. So reload
> + * memcg id. More details see the comments
> + * in memcg_reparent_list_lrus().
> + */
> + index = READ_ONCE(table[i].memcg->kmemcg_id);
> + if (index < 0)
> + xas_set_err(&xas, 0);
> + else if (!xas_error(&xas) && index != xas.xa_index)
> + xas_set(&xas, index);
> + goto retry;
> + }
> + }
> }
> + /* xas_nomem() is used to free memory instead of memory allocation. */
> + if (xas.xa_alloc)
> + xas_nomem(&xas, gfp);
> + xas_unlock_irqrestore(&xas, flags);
> kfree(table);
>
> + return xas_error(&xas);
> }
This is really unidiomatic. And so much more complicated than it needs
to be.
while (i--) {
do {
int index = READ_ONCE(table[i].memcg->kmemcg_id);
struct list_lru_per_memcg *mlru = table[i].mlru;
xas_set(&xas, index);
xas_lock_irqsave(&xas, flags);
if (index < 0 || xas_load(&xas))
xas_set_err(&xas, -EBUSY);
xas_store(&xas, mlru);
if (!xas_error(&xas))
break;
xas_unlock_irqrestore(&xas, flags);
} while (xas_nomem(&xas, gfp));
if (xas_error(&xas))
kfree(mlru);
}
kfree(table);
return xas_error(&xas);
(you might want to mask out the EBUSY error here)
next prev parent reply other threads:[~2022-03-31 15:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 12:21 [PATCH v6 00/16] Optimize list lru memory consumption Muchun Song
2022-02-28 12:21 ` [PATCH v6 01/16] mm: list_lru: transpose the array of per-node per-memcg lru lists Muchun Song
2022-02-28 12:21 ` [PATCH v6 02/16] mm: introduce kmem_cache_alloc_lru Muchun Song
2022-02-28 12:21 ` [PATCH v6 03/16] fs: introduce alloc_inode_sb() to allocate filesystems specific inode Muchun Song
2022-02-28 12:21 ` [PATCH v6 04/16] fs: allocate inode by using alloc_inode_sb() Muchun Song
2022-02-28 12:21 ` [PATCH v6 05/16] f2fs: " Muchun Song
2022-02-28 12:21 ` [PATCH v6 06/16] nfs42: use a specific kmem_cache to allocate nfs4_xattr_entry Muchun Song
2022-02-28 12:21 ` [PATCH v6 07/16] mm: dcache: use kmem_cache_alloc_lru() to allocate dentry Muchun Song
2022-02-28 12:21 ` [PATCH v6 08/16] xarray: use kmem_cache_alloc_lru to allocate xa_node Muchun Song
2022-02-28 12:21 ` [PATCH v6 09/16] mm: memcontrol: move memcg_online_kmem() to mem_cgroup_css_online() Muchun Song
2022-02-28 12:21 ` [PATCH v6 10/16] mm: list_lru: allocate list_lru_one only when needed Muchun Song
2022-02-28 12:21 ` [PATCH v6 11/16] mm: list_lru: rename memcg_drain_all_list_lrus to memcg_reparent_list_lrus Muchun Song
2022-02-28 12:21 ` [PATCH v6 12/16] mm: list_lru: replace linear array with xarray Muchun Song
2022-03-31 3:26 ` NeilBrown
2022-03-31 3:52 ` Muchun Song
2022-03-31 4:24 ` NeilBrown
2022-03-31 6:16 ` Muchun Song
2022-03-31 22:36 ` NeilBrown
2022-04-01 2:29 ` Muchun Song
2022-03-31 15:01 ` Matthew Wilcox [this message]
2022-04-01 3:23 ` Muchun Song
2022-02-28 12:21 ` [PATCH v6 13/16] mm: memcontrol: reuse memory cgroup ID for kmem ID Muchun Song
2022-02-28 12:21 ` [PATCH v6 14/16] mm: memcontrol: fix cannot alloc the maximum memcg ID Muchun Song
2022-02-28 12:21 ` [PATCH v6 15/16] mm: list_lru: rename list_lru_per_memcg to list_lru_memcg Muchun Song
2022-02-28 12:21 ` [PATCH v6 16/16] mm: memcontrol: rename memcg_cache_id to memcg_kmem_id Muchun Song
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=YkXCWW7ru9Gxyy6G@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=anna.schumaker@netapp.com \
--cc=chao@kernel.org \
--cc=david@fromorbit.com \
--cc=duanxiongchun@bytedance.com \
--cc=fam.zheng@bytedance.com \
--cc=hannes@cmpxchg.org \
--cc=jaegeuk@kernel.org \
--cc=kari.argillander@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=smuchun@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=trond.myklebust@hammerspace.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=zhengqi.arch@bytedance.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