From: David Howells <dhowells@redhat.com>
To: Eric Van Hensbergen <ericvh@kernel.org>,
Dominique Martinet <asmadeus@codewreck.org>,
Latchesar Ionkov <lucho@ionkov.net>
Cc: David Howells <dhowells@redhat.com>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Matthew Wilcox <willy@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
Christian Brauner <christian@brauner.io>,
netfs@lists.linux.dev, v9fs@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/3] 9p: Further netfslib-related changes
Date: Mon, 29 Jan 2024 11:54:34 +0000 [thread overview]
Message-ID: <20240129115512.1281624-1-dhowells@redhat.com> (raw)
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(-)
next reply other threads:[~2024-01-29 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:54 David Howells [this message]
2024-01-29 11:54 ` [RFC PATCH 1/3] 9p: Enable large folio support David Howells
2024-01-29 11:54 ` [RFC PATCH 2/3] 9p: Make better use of netfslib's writethrough caching David Howells
2024-01-29 11:54 ` [RFC PATCH 3/3] 9p: Always update remote_i_size in stat2inode David Howells
2024-01-29 14:14 ` [RFC PATCH 0/3] 9p: Further netfslib-related changes Christian Schoenebeck
2024-01-29 14:22 ` David Howells
2024-01-29 20:53 ` Christian Schoenebeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240129115512.1281624-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=christian@brauner.io \
--cc=ericvh@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netfs@lists.linux.dev \
--cc=v9fs@lists.linux.dev \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).