From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <trondmy@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: dhowells@redhat.com, Dave Wysochanski <dwysocha@redhat.com>,
Jeff Layton <jlayton@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
linux-nfs@vger.kernel.org, linux-cachefs@redhat.com
Subject: How to handle NFS patches for fscache I/O partial rewrite?
Date: Mon, 25 Jan 2021 22:10:50 +0000 [thread overview]
Message-ID: <2543104.1611612650@warthog.procyon.org.uk> (raw)
Hi Trond, Anna,
As you may have seen, I've managed to cut down the fscache overhaul to add a
glue layer to handle reads and switch to using async DIO through kiocbs rather
than using sync write and async reads with page wait list snooping. All the
rest of the API is unchanged (for the moment).
The glue layer (netfs helper library) handles the new VM readahead stuff and
reading transparent huge pages on behalf of the netfs, plus read shaping,
splitting and retrying.
Dave Wysochanski created some NFS patches for it, which I posted as part of my
branch. I'd like to get them into linux-next with an eye to having them
pulled by Linus in the next merge window, along with the rest of my branch.
Should I keep them in my branch and thence into linux-next, or do they need to
go through one of your branches?
Thanks,
David
reply other threads:[~2021-01-25 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2543104.1611612650@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=dwysocha@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--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