[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y35YE8wUtmplpInd@cmpxchg.org>
Date: Wed, 23 Nov 2022 12:27:47 -0500
From: Johannes Weiner <hannes@...xchg.org>
To: Nhat Pham <nphamcs@...il.com>
Cc: senozhatsky@...omium.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, minchan@...nel.org,
ngupta@...are.org, akpm@...ux-foundation.org, sjenning@...hat.com,
ddstreet@...e.org, vitaly.wool@...sulko.com
Subject: Re: [PATCH v6 6/6] zsmalloc: Implement writeback mechanism for
zsmalloc
On Wed, Nov 23, 2022 at 08:30:44AM -0800, Nhat Pham wrote:
> I'll put it right after releasing the pool's lock in the retry loop:
>
> /* Lock out object allocations and object compaction */
> remove_zspage(class, zspage, fullness);
>
> spin_unlock(&pool->lock);
> cond_resched();
>
> /* Lock backing pages into place */
> lock_zspage(zspage);
>
> This will also appear in v7. In the meantime, please feel free to discuss all
> the patches - I'll try to batch the changes to minimize the churning.
Oh, our emails collided. This is easier than my version :)
Powered by blists - more mailing lists