[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <lhnik2s7hfylqp252h3y4oz6dzqit63qh7jb5hn3k66kxjrxib@fczcv2pgk6t5>
Date: Wed, 29 Jan 2025 08:01:56 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Yosry Ahmed <yosry.ahmed@...ux.dev>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>, Minchan Kim <minchan@...nel.org>,
Johannes Weiner <hannes@...xchg.org>, Nhat Pham <nphamcs@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 5/6] zsmalloc: introduce handle mapping API
On (25/01/28 17:22), Yosry Ahmed wrote:
> On Tue, Jan 28, 2025 at 08:10:10PM +0900, Sergey Senozhatsky wrote:
> > On (25/01/28 14:29), Sergey Senozhatsky wrote:
> > > Maybe we can teach compaction and migration to try-WRITE and
> > > bail out if the page is locked, but I don't know.
> >
> > This seems to be working just fine.
>
> Does this mean we won't need as much locking changes to get zsmalloc to
> be preemtible?
Correct, only zspage lock is getting converted.
Powered by blists - more mailing lists