linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	akpm@linux-foundation.org, willy@infradead.org,
	miklos@szeredi.hu,
	"Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Subject: [PATCH 0/5] Removing the lru_cache_add() wrapper
Date: Tue,  1 Nov 2022 10:53:21 -0700	[thread overview]
Message-ID: <20221101175326.13265-1-vishal.moola@gmail.com> (raw)

This patchset replaces all calls of lru_cache_add() with the folio
equivalent: folio_add_lru(). This is allows us to get rid of the wrapper 
The series passes xfstests and the userfaultfd selftests.

I haven't been able to hit the fuse_try_move_page() function, so I
haven't been able to test those changes. Since replace_page_cache_page()
is only called by fuse_try_move_page() I haven't been able to test that
as well. Testing and review of both would be beneficial.

Vishal Moola (Oracle) (5):
  filemap: Convert replace_page_cache_page() to
    replace_page_cache_folio()
  fuse: Convert fuse_try_move_page() to use folios
  userfualtfd: Replace lru_cache functions with folio_add functions
  khugepage: Replace lru_cache_add() with folio_add_lru()
  folio-compat: Remove lru_cache_add()

 fs/fuse/dev.c           | 55 +++++++++++++++++++++--------------------
 include/linux/pagemap.h |  2 +-
 include/linux/swap.h    |  1 -
 mm/filemap.c            | 52 +++++++++++++++++++-------------------
 mm/folio-compat.c       |  6 -----
 mm/khugepaged.c         | 11 ++++++---
 mm/truncate.c           |  2 +-
 mm/userfaultfd.c        |  6 +++--
 mm/workingset.c         |  2 +-
 9 files changed, 67 insertions(+), 70 deletions(-)

-- 
2.38.1


             reply	other threads:[~2022-11-01 17:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 17:53 Vishal Moola (Oracle) [this message]
2022-11-01 17:53 ` [PATCH 1/5] filemap: Convert replace_page_cache_page() to replace_page_cache_folio() Vishal Moola (Oracle)
2022-11-01 18:20   ` Matthew Wilcox
2022-11-01 17:53 ` [PATCH 2/5] fuse: Convert fuse_try_move_page() to use folios Vishal Moola (Oracle)
2022-11-01 18:24   ` Matthew Wilcox
2022-11-10 18:36     ` Vishal Moola
2022-11-14 13:25       ` Miklos Szeredi
2022-11-01 17:53 ` [PATCH 3/5] userfualtfd: Replace lru_cache functions with folio_add functions Vishal Moola (Oracle)
2022-11-01 18:31   ` Matthew Wilcox
2022-11-02 19:02     ` Peter Xu
2022-11-02 19:21       ` Matthew Wilcox
2022-11-02 20:44         ` Peter Xu
2022-11-03 17:34           ` Axel Rasmussen
2022-11-03 17:56             ` Peter Xu
2022-11-02 20:47       ` Andrew Morton
2022-11-01 17:53 ` [PATCH 4/5] khugepage: Replace lru_cache_add() with folio_add_lru() Vishal Moola (Oracle)
2022-11-01 18:32   ` Matthew Wilcox
2022-11-01 17:53 ` [PATCH 5/5] folio-compat: Remove lru_cache_add() Vishal Moola (Oracle)
2022-11-01 18:33   ` Matthew Wilcox
2022-11-29 19:25 ` [PATCH 0/5] Removing the lru_cache_add() wrapper Vishal Moola

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=20221101175326.13265-1-vishal.moola@gmail.com \
    --to=vishal.moola@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=miklos@szeredi.hu \
    --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).