linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Christian Brauner <brauner@kernel.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: [PATCH 0/4] Use folio APIs in procfs
Date: Wed,  3 Apr 2024 18:14:51 +0100	[thread overview]
Message-ID: <20240403171456.1445117-1-willy@infradead.org> (raw)

Not sure whether Andrew or Christian will want to take this set of
fixes.  We're down to very few users of the PageFoo macros, with proc
being a major user.  After this patchset and another patchset I have
for khugepaged, we can get rid of PageActive, PageReadahead and
PageSwapBacked.

This patchset has the usual advantages in its own right of removing
hidden calls to compound_head().  We have the page table lock, so
the mapcount & refcount are stable and there can't be any races with
folios suddenly becoming tail pages.

Matthew Wilcox (Oracle) (4):
  proc: Convert gather_stats to use a folio
  proc: Convert smaps_page_accumulate to use a folio
  proc: Pass a folio to smaps_page_accumulate()
  proc: Convert smaps_pmd_entry to use a folio

 fs/proc/task_mmu.c | 37 ++++++++++++++++++++-----------------
 1 file changed, 20 insertions(+), 17 deletions(-)

-- 
2.43.0



             reply	other threads:[~2024-04-03 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 17:14 Matthew Wilcox (Oracle) [this message]
2024-04-03 17:14 ` [PATCH 1/4] proc: Convert gather_stats to use a folio Matthew Wilcox (Oracle)
2024-04-03 17:14 ` [PATCH 2/4] proc: Convert smaps_page_accumulate " Matthew Wilcox (Oracle)
2024-04-03 17:14 ` [PATCH 3/4] proc: Pass a folio to smaps_page_accumulate() Matthew Wilcox (Oracle)
2024-04-03 17:14 ` [PATCH 4/4] proc: Convert smaps_pmd_entry to use a folio Matthew Wilcox (Oracle)
2024-04-03 19:16 ` [PATCH 0/4] Use folio APIs in procfs Andrew Morton
2024-04-05 11:02   ` Christian Brauner

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=20240403171456.1445117-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).