Re: [PATCH v3 1/7] mm/lru: add per lruvec lock for memcg

From: Alex Shi
Date: Sun Nov 17 2019 - 21:45:16 EST




å 2019/11/16 äå2:28, Shakeel Butt åé:
> On Fri, Nov 15, 2019 at 7:15 PM Alex Shi <alex.shi@xxxxxxxxxxxxxxxxx> wrote:
>>
>> Currently memcg still use per node pgdat->lru_lock to guard its lruvec.
>> That causes some lru_lock contention in a high container density system.
>>
>> If we can use per lruvec lock, that could relief much of the lru_lock
>> contention.
>>
>> The later patches will replace the pgdat->lru_lock with lruvec->lru_lock
>> and show the performance benefit by benchmarks.
>
> Merge this patch with actual usage. No need to have a separate patch.

Thanks for comment, Shakeel!

Yes, but considering the 3rd, huge and un-splitable patch of actully replacing, I'd rather to pull sth out from
it. Ty to make patches a bit more readable, Do you think so?

Thanks
Alex