RFC 9p: Further netfslib-related changes
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | 9p: Enable large folio supportfs/ | +1 | 0 replies | |
| 2/3 | 9p: Make better use of netfslib's writethrough cachingfs/ | +1 | 0 replies | |
| 3/3 | 9p: Always update remote_i_size in stat2inodefs/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] 9p: Further netfslib-related changes
Hi Eric, Dominique,
Here are some netfslib-related changes we might want to consider applying to 9p:
(1) Enable large folio support for 9p. This is handled entirely by netfslib and is already supported in afs. I wonder if we should limit the maximum folio size to 1MiB to match the maximum I/O size in the 9p protocol.
(2) Make better use of netfslib's writethrough caching support by not disabling caching for O_DSYNC. netfs_perform_write() will set up and dispatch write requests as it copies data into the pagecache.
(3) Always update netfs_inode::remote_size to reflect what we think the server's idea of the file size is. This is separate from inode::i_size which is our idea of what it should be if all of our outstanding dirty data is committed.
The patches can also be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-9p
Thanks,
David
David Howells (2):
9p: Make better use of netfslib's writethrough caching 9p: Always update remote_i_size in stat2inode
Dominique Martinet (1):
9p: Enable large folio support
fs/9p/fid.h | 3 +-- fs/9p/vfs_inode.c | 1 + fs/9p/vfs_inode_dotl.c | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-)