All of lore.kernel.org
 help / color / mirror / Atom feed
From: JeffleXu <jefflexu@linux.alibaba.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: dhowells@redhat.com, linux-cachefs@redhat.com, xiang@kernel.org,
	chao@kernel.org, linux-erofs@lists.ozlabs.org,
	linux-fsdevel@vger.kernel.org, joseph.qi@linux.alibaba.com,
	bo.liu@linux.alibaba.com, tao.peng@linux.alibaba.com,
	gerry@linux.alibaba.com, eguan@linux.alibaba.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 19/23] cachefiles: implement .demand_read() for demand read
Date: Thu, 20 Jan 2022 20:43:57 +0800	[thread overview]
Message-ID: <a5b495d3-cafe-548a-2130-b7aa9e597f41@linux.alibaba.com> (raw)
In-Reply-To: <YegQOHs9yjIgu1Qi@casper.infradead.org>



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

WARNING: multiple messages have this Message-ID (diff)
From: JeffleXu <jefflexu@linux.alibaba.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com,
	joseph.qi@linux.alibaba.com, linux-cachefs@redhat.com,
	linux-fsdevel@vger.kernel.org, gerry@linux.alibaba.com,
	linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v1 19/23] cachefiles: implement .demand_read() for demand read
Date: Thu, 20 Jan 2022 20:43:57 +0800	[thread overview]
Message-ID: <a5b495d3-cafe-548a-2130-b7aa9e597f41@linux.alibaba.com> (raw)
In-Reply-To: <YegQOHs9yjIgu1Qi@casper.infradead.org>



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

  reply	other threads:[~2022-01-20 12:44 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27 12:54 [PATCH v1 00/23] fscache,erofs: fscache-based demand-read semantics Jeffle Xu
2021-12-27 12:54 ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 01/23] cachefiles: add cachefiles_demand devnode Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-28  2:47   ` Joseph Qi
2021-12-28  2:47     ` Joseph Qi
2021-12-28 12:34     ` JeffleXu
2021-12-28 12:34       ` JeffleXu
2021-12-27 12:54 ` [PATCH v1 02/23] cachefiles: add mode command to distinguish modes Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 03/23] cachefiles: detect backing file size in demand-read mode Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 04/23] netfs: make ops->init_rreq() optional Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 05/23] netfs: add inode parameter to netfs_alloc_read_request() Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2022-01-04 14:00   ` Gao Xiang
2022-01-04 14:00     ` Gao Xiang
2022-01-13  3:10   ` [Linux-cachefs] " JeffleXu
2022-01-13  3:10     ` JeffleXu
2022-01-13 12:09     ` Gao Xiang
2022-01-13 12:09       ` Gao Xiang
2021-12-27 12:54 ` [PATCH v1 06/23] erofs: export erofs_map_blocks() Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 07/23] erofs: add nodev mode Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2022-01-04 14:33   ` Gao Xiang
2022-01-04 14:33     ` Gao Xiang
2022-01-04 14:58     ` Gao Xiang
2022-01-04 14:58       ` Gao Xiang
2022-01-05  9:04       ` JeffleXu
2021-12-27 12:54 ` [PATCH v1 08/23] erofs: register global fscache volume Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 09/23] erofs: add cookie context helper functions Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 10/23] erofs: add anonymous inode managing page cache of blob file Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 11/23] erofs: register cookie context for bootstrap Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 12/23] erofs: implement fscache-based metadata read Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 17:07   ` kernel test robot
2021-12-27 17:07     ` kernel test robot
2021-12-27 17:07     ` kernel test robot
2021-12-27 17:17   ` kernel test robot
2021-12-27 17:17     ` kernel test robot
2021-12-27 17:17     ` kernel test robot
2021-12-27 12:54 ` [PATCH v1 13/23] erofs: implement fscache-based data read Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2022-01-03  6:32   ` JeffleXu
2022-01-03  6:32     ` JeffleXu
2022-01-04 14:40   ` Gao Xiang
2022-01-04 14:40     ` Gao Xiang
2022-01-05  2:29     ` JeffleXu
2021-12-27 12:54 ` [PATCH v1 14/23] erofs: register cookie context for data blobs Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 15/23] erofs: implement fscache-based data read " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 16/23] erofs: add 'uuid' mount option Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 17/23] netfs: support on demand read Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 18/23] cachefiles: use idr tree managing pending " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 19/23] cachefiles: implement .demand_read() for " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 15:32   ` kernel test robot
2021-12-27 15:32     ` kernel test robot
2021-12-27 15:32     ` kernel test robot
2021-12-27 15:36   ` Matthew Wilcox
2021-12-27 15:36     ` Matthew Wilcox
2021-12-28 12:33     ` JeffleXu
2021-12-28 12:33       ` JeffleXu
2022-01-12  9:02       ` JeffleXu
2022-01-12  9:02         ` JeffleXu
2022-01-19 13:20         ` Matthew Wilcox
2022-01-19 13:20           ` Matthew Wilcox
2022-01-20 12:43           ` JeffleXu [this message]
2022-01-20 12:43             ` JeffleXu
2021-12-27 15:55   ` kernel test robot
2021-12-27 15:55     ` kernel test robot
2021-12-27 15:55     ` kernel test robot
2021-12-27 12:54 ` [PATCH v1 20/23] cachefiles: implement .poll() " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 21/23] cachefiles: implement .read() " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 22/23] cachefiles: add done command " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu
2021-12-27 12:54 ` [PATCH v1 23/23] erofs: support on " Jeffle Xu
2021-12-27 12:54   ` Jeffle Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a5b495d3-cafe-548a-2130-b7aa9e597f41@linux.alibaba.com \
    --to=jefflexu@linux.alibaba.com \
    --cc=bo.liu@linux.alibaba.com \
    --cc=chao@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=eguan@linux.alibaba.com \
    --cc=gerry@linux.alibaba.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tao.peng@linux.alibaba.com \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.