Re: [PATCH 00/14] per memcg lru_lock

From: Alex Shi
Date: Mon Aug 26 2019 - 10:25:45 EST

å 2019/8/22 äå11:20, Daniel Jordan åé:
>>> ÂÂ>
>>> It's also synthetic but it stresses lru_lock more than just anon alloc/free. It hits the page activate path, which is where we see this lock in our database, and if enough memory is configured lru_lock also gets stressed during reclaim, similar to [1].
>> Thanks for the sharing, this patchset can not help the [1] case, since it's just relief the per container lock contention now.
> I should've been clearer. [1] is meant as an example of someone suffering from lru_lock during reclaim. Wouldn't your series help per-memcg reclaim?

yes, I got your point, since the aim9 don't show much improvement, I am trying this case in containers.