[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a5b495d3-cafe-548a-2130-b7aa9e597f41@linux.alibaba.com>
Date: Thu, 20 Jan 2022 20:43:57 +0800
From: JeffleXu <jefflexu@...ux.alibaba.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: dhowells@...hat.com, linux-cachefs@...hat.com, xiang@...nel.org,
chao@...nel.org, linux-erofs@...ts.ozlabs.org,
linux-fsdevel@...r.kernel.org, joseph.qi@...ux.alibaba.com,
bo.liu@...ux.alibaba.com, tao.peng@...ux.alibaba.com,
gerry@...ux.alibaba.com, eguan@...ux.alibaba.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 19/23] cachefiles: implement .demand_read() for demand
read
On 1/19/22 9:20 PM, Matthew Wilcox wrote:
> On Wed, Jan 12, 2022 at 05:02:13PM +0800, JeffleXu wrote:
>> I'm afraid IDR can't be replaced by xarray here. Because we need an 'ID'
>> for each pending read request, so that after fetching data from remote,
>> user daemon could notify kernel which read request has finished by this
>> 'ID'.
>>
>> Currently this 'ID' is get from idr_alloc(), and actually identifies the
>> position of corresponding read request inside the IDR tree. I can't find
>> similar API of xarray implementing similar function, i.e., returning an
>> 'ID'.
>
> xa_alloc().
>
Oh yes. Thanks. I will try to convert to xarray API...
--
Thanks,
Jeffle
Powered by blists - more mailing lists