[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8f73d28e-db30-f2e4-0143-9d75c4b13087@linux.alibaba.com>
Date: Thu, 27 Jan 2022 15:07:00 +0800
From: JeffleXu <jefflexu@...ux.alibaba.com>
To: David Howells <dhowells@...hat.com>
Cc: 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 v2 00/20] fscache,erofs: fscache-based demand-read
semantics
On 1/26/22 4:51 PM, David Howells wrote:
> JeffleXu <jefflexu@...ux.alibaba.com> wrote:
>
>> "/path/to/file+offset"
>> ^
>>
>> Besides, what does the 'offset' mean?
>
> Assuming you're storing multiple erofs files within the same backend file, you
> need to tell the the cache backend how to find the data. Assuming the erofs
> data is arranged such that each erofs file is a single contiguous region, then
> you need a pathname and a file offset to find one of them.
>
Alright. In fact one erofs file can contain multiple chunks, which can
correspond to different backing blob files. Thus currently I will use
fscache_read() directly, to push this feature forward.
Thanks a lot.
--
Thanks,
Jeffle
Powered by blists - more mailing lists