From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
linux-mm@kvack.org, linux-cachefs@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Request for folios
Date: Tue, 13 Jul 2021 19:11:01 -0700 [thread overview]
Message-ID: <20210713191101.b38013786e36286e78c9648c@linux-foundation.org> (raw)
In-Reply-To: <3398985.1626104609@warthog.procyon.org.uk>
On Mon, 12 Jul 2021 16:43:29 +0100 David Howells <dhowells@redhat.com> wrote:
> Hi Andrew,
>
> Is it possible to get Willy's folios patchset - or at least the core of it -
> staged for the next merge window? I'm working on improvements to the local
> filesystem caching code and the network filesystem support library and that
> involves a lot of dealing with pages - all of which will need to be converted
> to the folios stuff. This has the potential to conflict with the changes
> Willy's patches make to filesystems. Further, the folios patchset offers some
> facilities that make my changes a bit easier - and some changes that make
> things a bit more challenging (e.g. page size becoming variable).
It's about that time. However there's a discussion at present which
might result in significant renamings, so I'll wait until that has
panned out.
> Also, is it possible to get the folios patchset in a stable public git branch
> that I can base my patches upon?
I guess Willy's tree, but I doubt if the folio patches will be reliably
stable for some time (a few weeks?)
next prev parent reply other threads:[~2021-07-14 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 15:43 Request for folios David Howells
2021-07-14 2:11 ` Andrew Morton [this message]
2021-07-15 19:39 ` Matthew Wilcox
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=20210713191101.b38013786e36286e78c9648c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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).