[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd44a613-d820-6085-0145-657078fd79cc@linux.alibaba.com>
Date: Mon, 26 Aug 2019 22:16:58 +0800
From: Alex Shi <alex.shi@...ux.alibaba.com>
To: Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Tejun Heo <tj@...nel.org>
Cc: Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Hugh Dickins <hughd@...gle.com>
Subject: Re: [PATCH 03/14] lru/memcg: using per lruvec lock in
un/lock_page_lru
在 2019/8/26 下午4:30, Konstantin Khlebnikov 写道:
>>
>>
>
> What protects lruvec from freeing at this point?
> After reading resolving lruvec page could be moved and cgroup deleted.
>
> In this old patches I've used RCU for that: https://lkml.org/lkml/2012/2/20/276
> Pointer to lruvec should be resolved under disabled irq.
> Not sure this works these days.
Thanks for reminder! I will reconsider this point and come up with changes.
Thanks
Alex
Powered by blists - more mailing lists