[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5ed6a7fa-31e0-4516-8cbf-8a725377aa32@gmail.com>
Date: Tue, 30 Jul 2024 19:38:40 +0800
From: Alex Shi <seakeel@...il.com>
To: Sergey Senozhatsky <senozhatsky@...omium.org>, alexs@...nel.org
Cc: 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 18/22] mm/zsmalloc: introduce __zpdesc_clear_movable
On 7/30/24 5:34 PM, Sergey Senozhatsky wrote:
> On (24/07/29 19:25), alexs@...nel.org wrote:
> [..]
>> +static inline void __zpdesc_clear_movable(struct zpdesc *zpdesc)
>> +{
>> + __ClearPageMovable(zpdesc_page(zpdesc));
>> +}
>
> [..]
>
>> @@ -846,7 +846,7 @@ static void reset_zpdesc(struct zpdesc *zpdesc)
>> {
>> struct page *page = zpdesc_page(zpdesc);
>>
>> - __ClearPageMovable(page);
>> + __zpdesc_clear_movable(zpdesc);
>> ClearPagePrivate(page);
>
> Just a quick question, I see that you wrote wrappers for pretty
> much everything, including SetPagePrivate(), but not for
> ClearPagePrivate()?
Hi Sergey,
Thanks for comment!
Yes, it's better to have one for clear, I'll sent a patch soon.
Alex
Powered by blists - more mailing lists