[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b78b8183-4dbc-4163-a84b-f74f5af97e84@huaweicloud.com>
Date: Tue, 10 Dec 2024 19:35:43 +0800
From: Chen Ridong <chenridong@...weicloud.com>
To: Shakeel Butt <shakeel.butt@...ux.dev>, Hugh Dickins <hughd@...gle.com>
Cc: Yu Zhao <yuzhao@...gle.com>, akpm@...ux-foundation.org,
mhocko@...nel.org, hannes@...xchg.org, yosryahmed@...gle.com,
roman.gushchin@...ux.dev, muchun.song@...ux.dev, davidf@...eo.com,
vbabka@...e.cz, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, chenridong@...wei.com, wangweiyang2@...wei.com
Subject: Re: [next -v1 3/5] memcg: simplify the mem_cgroup_update_lru_size
function
On 2024/12/7 5:20, Shakeel Butt wrote:
> On Fri, Dec 06, 2024 at 12:24:54AM -0800, Hugh Dickins wrote:
> [...]
>> Another thing to understand: it's called before adding folio to list,
>> but after removing folio from list: when it can usefully compare whether
>> the emptiness of the list correctly matches lru_size 0.
>
> I think one source of confusion might be that this "emptiness" check has
> been removed by commit b4536f0c829c because of maintaining the list size
> per-zone and actual list is shared between zones of a node.
>
Agree.
Maybe it doesn't have to distinguish between "size > 0" and "size < 0" now?
Thanks,
Ridong
>> It cannot do so
>> when adding if you "simplify" it in the way that you did.
>>
Powered by blists - more mailing lists