From: Muchun Song <muchun.song@linux.dev>
To: Jingxiang Zeng <linuszeng@tencent.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
hannes@cmpxchg.org, mhocko@kernel.org, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, chengming.zhou@linux.dev,
kasong@tencent.com, lkp@intel.com
Subject: Re: [PATCH V1] mm/list_lru: make the case where mlru is NULL as unlikely
Date: Thu, 27 Feb 2025 20:19:42 +0800 [thread overview]
Message-ID: <3FFDDAF8-CB31-4089-B8E7-3CA2EDBFE999@linux.dev> (raw)
In-Reply-To: <20250227082223.1173847-1-jingxiangzeng.cas@gmail.com>
> On Feb 27, 2025, at 16:22, Jingxiang Zeng <jingxiangzeng.cas@gmail.com> wrote:
>
> From: Zeng Jingxiang <linuszeng@tencent.com>
>
> In the following memcg_list_lru_alloc() function, mlru here is almost
> always NULL, so in most cases this should save a function call, mark
> mlru as unlikely to optimize the code, and reusing the mlru for the
> next attempt when the tree insertion fails.
> do {
> xas_lock_irqsave(&xas, flags);
> if (!xas_load(&xas) && !css_is_dying(&pos->css)) {
> xas_store(&xas, mlru);
> if (!xas_error(&xas))
> mlru = NULL;
> }
> xas_unlock_irqrestore(&xas, flags);
> } while (xas_nomem(&xas, GFP_KERNEL));
>> if (mlru)
> kfree(mlru);
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202412290924.UTP7GH2Z-lkp@intel.com/
> Signed-off-by: Zeng Jingxiang <linuszeng@tencent.com>
> Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
Reviewed-by: Muchun Song <muchun.song@linux.dev>
Thanks.
next prev parent reply other threads:[~2025-02-27 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 8:22 [PATCH V1] mm/list_lru: make the case where mlru is NULL as unlikely Jingxiang Zeng
2025-02-27 12:19 ` Muchun Song [this message]
2025-02-27 14:42 ` Johannes Weiner
2025-02-27 18:54 ` Shakeel Butt
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=3FFDDAF8-CB31-4089-B8E7-3CA2EDBFE999@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linuszeng@tencent.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.