[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240801031304.GF16599@google.com>
Date: Thu, 1 Aug 2024 12:13:04 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Alex Shi <seakeel@...il.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, alexs@...nel.org,
Vitaly Wool <vitaly.wool@...sulko.com>,
Miaohe Lin <linmiaohe@...wei.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
minchan@...nel.org, willy@...radead.org, david@...hat.com,
42.hyeyoo@...il.com, Yosry Ahmed <yosryahmed@...gle.com>,
nphamcs@...il.com
Subject: Re: [PATCH v4 22/22] mm/zsmalloc: update comments for page->zpdesc
changes
On (24/07/31 12:14), Alex Shi wrote:
> > A bit of a different thing, still documentation related tho: do
> > we want to do something about comments that mention page_lock in
> > zsmalloc.c?
>
> Good question!
>
> There are some comments mentioned about the page_lock in the file, but missed
> in the header of file, so how about the following adding:
And e.g. things like
`The page locks trylock_zspage got will be released by __free_zspage.`
Should this (and the rest) spell "zpdesc locks" or something? Or do
we still want to refer to it as "page lock"?
Powered by blists - more mailing lists