linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] Merge PG_private_2 and PG_mappedtodisk
Date: Thu, 15 Aug 2024 23:41:23 +0200	[thread overview]
Message-ID: <7e7ee391-6f4d-4d36-ace5-4f8ca81479bc@redhat.com> (raw)
In-Reply-To: <ZrzrIEDcJRFHOTNh@casper.infradead.org>

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?

> 
> $ git grep -El '(folio.*mappedtodisk)|PageMappedToDisk'
> fs/buffer.c
> fs/ext4/readpage.c
> fs/f2fs/data.c
> fs/f2fs/file.c
> fs/fuse/dev.c
> fs/mpage.c
> fs/nilfs2/file.c
> fs/nilfs2/page.c
> include/trace/events/pagemap.h
> mm/memory.c
> mm/migrate.c
> mm/truncate.c
> 
> $ git grep -El '(folio.*private_2)|PagePrivate2'
> fs/btrfs/ctree.h
> fs/ceph/addr.c
> fs/netfs/buffered_read.c
> fs/netfs/fscache_io.c
> fs/netfs/io.c
> fs/nfs/file.c
> fs/nfs/fscache.h
> fs/nfs/write.c
> include/linux/netfs.h
> include/linux/pagemap.h
> mm/filemap.c
> mm/migrate.c
> 
> 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.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-08-15 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 17:36 Matthew Wilcox
2024-08-15 21:41 ` David Hildenbrand [this message]
2024-08-16  3:42   ` 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=7e7ee391-6f4d-4d36-ace5-4f8ca81479bc@redhat.com \
    --to=david@redhat.com \
    --cc=linux-fsdevel@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