lkml.org 
[lkml]   [2021]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [Linux-cachefs] [RFC 09/19] netfs: refactor netfs_rreq_unlock()
From


On 12/11/21 1:23 PM, JeffleXu wrote:
>
>
> On 12/10/21 11:41 PM, David Howells wrote:
>> Jeffle Xu <jefflexu@linux.alibaba.com> wrote:
>>
>>> In demand-read case, the input folio of netfs API is may not the page
>>
>> "is may not the page"? I think you're missing a verb (and you have too many
>> auxiliary verbs;-)
>>
>
> Sorry for my poor English... What I want to express is that
>
> "In demand-read case, the input folio of netfs API may not be the page
> cache inside the address space of the netfs file."
>

By the way, can we change the current address_space based netfs API to
folio-based, which shall be more general? That is, the current
implementation of netfs API uses (address_space, page_offset, len) tuple
to describe the destination where the read data shall be store into.
While in the demand-read case, the input folio may not be the page
cache, and thus there's no address_space attached with it.

--
Thanks,
Jeffle

\
 
 \ /
  Last update: 2022-09-17 16:12    [W:0.108 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site