> On Jan 31, 2022, at 4:06 PM, David Howells <dhowells@xxxxxxxxxx> wrote: > > I've been working on a library (in fs/netfs/) to provide network filesystem > support services, with help particularly from Jeff Layton. The idea is to > move the common features of the VM interface, including request splitting, > operation retrying, local caching, content encryption, bounce buffering and > compression into one place so that various filesystems can share it. IIUC this suite of functions is beneficial mainly to clients, is that correct? I'd like to be clear about that, this is not an objection to the topic. I'm interested in discussing how folios might work for the NFS _server_, perhaps as a separate or adjunct conversation. > This also intersects with the folios topic as one of the reasons for this now > is to hide as much of the existence of folios/pages from the filesystem, > instead giving it persistent iov iterators to describe the buffers available > to it. > > It could be useful to get various network filesystem maintainers together to > discuss it and how to do parts of it and how to roll it out into more > filesystems if it suits them. This might qualify more for a BoF session than > a full FS track session. > > Further, discussion of designing a more effective cache backend could be > useful. I'm thinking along the lines of something that can store its data on > a single file (or a raw blockdev) with indexing along the lines of what > filesystem drivers such as openafs do. > > David > -- Chuck Lever
