Re: [PATCH v21 18/19] mm/lru: introduce the relock_page_lruvec function

On 11/5/20 9:55 AM, Alex Shi wrote: From: Alexander Duyck Use this new function to replace repeated same code, no func change. When testing for relock we can avoid the need for RCU locking if we simply compare the page pgdat and memcg pointers versus those that the lruvec is holding. By doing

Re: [PATCH v21 18/19] mm/lru: introduce the relock_page_lruvec function

On Fri, Nov 06, 2020 at 03:50:22PM +0800, Alex Shi wrote: > From 6c142eb582e7d0dbf473572ad092eca07ab75221 Mon Sep 17 00:00:00 2001 > From: Alexander Duyck > Date: Tue, 26 May 2020 17:31:15 +0800 > Subject: [PATCH v21 18/19] mm/lru: introduce the relock_page_lruvec function >

Re: [PATCH v21 18/19] mm/lru: introduce the relock_page_lruvec function

在 2020/11/5 下午4:55, Alex Shi 写道: > From: Alexander Duyck update the patch on page_memcg() change: >From 6c142eb582e7d0dbf473572ad092eca07ab75221 Mon Sep 17 00:00:00 2001 From: Alexander Duyck Date: Tue, 26 May 2020 17:31:15 +0800 Subject: [PATCH v21 18/19] mm/lru: introdu

[PATCH v21 18/19] mm/lru: introduce the relock_page_lruvec function

From: Alexander Duyck Use this new function to replace repeated same code, no func change. When testing for relock we can avoid the need for RCU locking if we simply compare the page pgdat and memcg pointers versus those that the lruvec is holding. By doing this we can avoid the extra pointer wa