Re: [PATCH v18 21/32] mm/lru: introduce the relock_page_lruvec function

On Mon, 24 Aug 2020, 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 >

[PATCH v18 21/32] 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