From: Waiman Long <longman@redhat.com>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH] mm/list_lru: Optimize memcg_drain_list_lru_node()
Date: Tue, 8 Mar 2022 10:41:38 -0500 [thread overview]
Message-ID: <3faa2be7-3a08-ee6d-35e8-c4a35e825c77@redhat.com> (raw)
In-Reply-To: <YibeERR3Nmh7+9ZA@carbon.dhcp.thefacebook.com>
On 3/7/22 23:39, Roman Gushchin wrote:
> On Mon, Mar 07, 2022 at 10:30:09PM -0500, Waiman Long wrote:
>> Since commit 2c80cd57c743 ("mm/list_lru.c: fix list_lru_count_node()
>> to be race free"), we are tracking the total number of lru
>> entries in a list_lru_node in its nr_items field. In the case of
>> memcg_drain_list_lru_node(), there is nothing to be done if nr_items
>> is 0. We don't even need to take the nlru->lock as no new lru entry
>> could be added by a racing list_lru_add() to the draining src_idx memcg
>> at this point.
>>
>> Signed-off-by: Waiman Long <longman@redhat.com>
> Hi Waiman!
>
> The patch makes total sense to me, however it needs to be rebased at least
> on top of "mm: list_lru: rename memcg_drain_all_list_lrus to memcg_reparent_list_lrus".
>
> Thanks!
>
>
This patch was based on the current linux-next tree which includes
commit ff221bc26bdd ("mm: list_lru: rename memcg_drain_all_list_lrus to
memcg_reparent_list_lrus"). I do remember to double-check linux-next
before sending this patch out. In fact, the same patch can be applied to
both linux and linux-next tree without problem.
Cheers,
Longman
next prev parent reply other threads:[~2022-03-08 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 3:30 Waiman Long
2022-03-08 4:39 ` Roman Gushchin
2022-03-08 15:41 ` Waiman Long [this message]
2022-03-09 0:17 ` Roman Gushchin
2022-03-09 0:50 ` Waiman Long
2022-03-09 1:06 ` Waiman Long
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=3faa2be7-3a08-ee6d-35e8-c4a35e825c77@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=songmuchun@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