19:32:01p_lebrasca: you have VFS handling "routing", then calling pagecache-based functions to load file contents (gross simplification there)
19:32:39p_lso, in a way, you have VFS(routing) -> filesystem driver -> VFS(pagecache) -> filesystem driver -> disk/etc
19:32:50p_lbut I'm not sure if it's a good way to go
19:34:16ebrascap_l: VFS -> file-cache -> filesystem -> disk
19:34:36p_lnow, a generic share-able buffer structure that could be used by all filesystems, and a way to mark "this part of address space has this handler for providing pages"
19:35:49p_lebrasca: that's when the filesystem uses the provided generic file_ops and just implements get_block_routine and inode read
19:37:40p_lwell... I might be not the most current, but in case of Linux VFS (which you referred to) it's the filesystem's choice to use "generic operations" (though it's *heavily* pushed to use them)
19:38:09ebrascap_l: I only get 1 image to get inspiration.
19:41:06p_lebrasca: in Linux, it's heavily suggested to use "generic" implementations of several things where possible