[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <125d6be2-eabb-16d1-19de-82c2e7de3851@cloud.ionos.com>
Date: Mon, 27 Apr 2020 10:10:05 +0200
From: Guoqing Jiang <guoqing.jiang@...ud.ionos.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
david@...morbit.com, willy@...radead.org,
Andrew Morton <akpm@...ux-foundation.org>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
William Kucharski <william.kucharski@...cle.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Andreas Gruenbacher <agruenba@...hat.com>,
Yang Shi <yang.shi@...ux.alibaba.com>,
Yafang Shao <laoar.shao@...il.com>
Subject: Re: [RFC PATCH 1/9] include/linux/pagemap.h: introduce
set/clear_fs_page_private
Hi Christoph,
On 4/27/20 7:52 AM, Christoph Hellwig wrote:
> Why not attach_page_private and clear_page_private as that conveys
> the use case a little better?
Yes, thanks for the good suggestion. Will rename them if no one else
has new idea ...
>> +static inline void *set_fs_page_private(struct page *page, void *data)
>> +{
>> + get_page(page);
>> + set_page_private(page, (unsigned long)data);
>> + SetPagePrivate(page);
>> +
>> + return data;
>> +}
>> +
>> +static inline void *clear_fs_page_private(struct page *page)
>> +{
>> + void *data = (void *)page_private(page);
>> +
>> + if (!PagePrivate(page))
>> + return NULL;
>> + ClearPagePrivate(page);
>> + set_page_private(page, 0);
>> + put_page(page);
>> +
>> + return data;
>> +}
> Can you add kerneldoc comments describing them, including why we
> take the refernces?
Ok, will do.
> Also what is the point of the return value of set_fs_page_private?
In this way, iomap_page_create can just return the function, but you
don't like this way as you replied, will change the return value to "void".
Thanks,
Guoqing
Powered by blists - more mailing lists