[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cbbcq3vklpcrwizvbjupsyczcv7ccnygys7pg3njbrpostw2lh@7kwgdoopeyy4>
Date: Thu, 13 Feb 2025 11:54:14 +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>, Kairui Song <ryncsn@...il.com>, Minchan Kim <minchan@...nel.org>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 10/18] zsmalloc: factor out pool locking helpers
On (25/02/13 01:12), Yosry Ahmed wrote:
> > I want to hide the details, keep them in one place and at some
> >
> > point *in the future* have the same "locking rules" as for zspage
> >
> > lock. Also *possibly* throwing a couple of lockdep assertions.
> >
> > So I'd prefer to abstract all of these.
>
>
> I'd prefer to introduce the abstractions when they are needed tbh. Right now they just make the code less readable.
OK, gone now. I think I didn't screw things up resolving the conflicts.
Powered by blists - more mailing lists