From: Matthew Wilcox <willy@infradead.org>
To: David Hildenbrand <david@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] Merge PG_private_2 and PG_mappedtodisk
Date: Fri, 16 Aug 2024 04:42:55 +0100 [thread overview]
Message-ID: <Zr7Kv0nR4_z9XaXx@casper.infradead.org> (raw)
In-Reply-To: <7e7ee391-6f4d-4d36-ace5-4f8ca81479bc@redhat.com>
On Thu, Aug 15, 2024 at 11:41:23PM +0200, David Hildenbrand wrote:
> On 14.08.24 19:36, Matthew Wilcox wrote:
> > I believe these two flags have entirely disjoint uses and there will
> > be no confusion in amalgamating them.
> >
> > Anonymous memory (re)uses mappedtodisk for anon_exclusive.
> > Anonymous memory does not use PG_private_2.
>
> Also not when they are in the swapcache, right?
Correct, swapcache has no use of PG_private_2.
> > The one thing that's going to stand in the way of this is that various
> > parts of the VFS treat private_2 as a "wait for this bit to be clear",
> > due to its use in fscache (which is going away).
> >
> > So my approach here is going to be:
> >
> > - Rename mappedtodisk to be PG_owner_priv_2 (add appropriate aliases)
> > - Switch btrfs to use owner_priv_2 instead of private_2
> > - Wait for the fscache use of private2 to finish its deprecation cycle
> > - Remove private_2 entirely
> >
> > Sound good?
>
> Yes, one step into the right direction.
Cool, thanks.
prev parent reply other threads:[~2024-08-16 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 17:36 [RFC] Merge PG_private_2 and PG_mappedtodisk Matthew Wilcox
2024-08-15 21:41 ` David Hildenbrand
2024-08-16 3:42 ` Matthew Wilcox [this message]
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=Zr7Kv0nR4_z9XaXx@casper.infradead.org \
--to=willy@infradead.org \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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).