linux-mm.kvack.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,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	Jordan Rome <linux@jordanrome.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Subject: [PATCH 0/3] Remove unmap_and_put_page()
Date: Wed,  9 Jul 2025 12:40:15 -0700	[thread overview]
Message-ID: <20250709194017.927978-3-vishal.moola@gmail.com> (raw)

This patchset uses folios in both the callers of
unmap_and_put_page(), saving a couple calls to compound_head() wrappers.

----

The initial rfc[1] attempted to provide large folio support for the
caller functions. Trying to do this without the relevant "struct page"
is excessive and unnecessary right now.

[1] https://lore.kernel.org/linux-mm/20250625174841.1094510-1-vishal.moola@gmail.com/

Vishal Moola (Oracle) (3):
  mm/memory.c: Use folios in __copy_remote_vm_str()
  mm/memory.c: Use folios in __access_remote_vm()
  mm: Remove unmap_and_put_page()

 include/linux/highmem.h |  6 ------
 mm/memory.c             | 16 ++++++++++------
 2 files changed, 10 insertions(+), 12 deletions(-)

-- 
2.50.0



             reply	other threads:[~2025-07-09 19:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 19:40 Vishal Moola (Oracle) [this message]
2025-07-09 19:40 ` [PATCH 1/3] mm/memory.c: Use folios in __copy_remote_vm_str() Vishal Moola (Oracle)
2025-07-11 10:49   ` David Hildenbrand
2025-07-09 19:40 ` [PATCH 2/3] mm/memory.c: Use folios in __access_remote_vm() Vishal Moola (Oracle)
2025-07-11 10:50   ` David Hildenbrand
2025-07-09 19:40 ` [PATCH 3/3] mm: Remove unmap_and_put_page() Vishal Moola (Oracle)
2025-07-11 10:51   ` David Hildenbrand

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=20250709194017.927978-3-vishal.moola@gmail.com \
    --to=vishal.moola@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@jordanrome.com \
    --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).