From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-mm@kvack.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Uladzislau Rezki <urezki@gmail.com>,
David Howells <dhowells@redhat.com>,
Dave Chinner <david@fromorbit.com>,
linux-fsdevel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ira Weiny <ira.weiny@intel.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH v2 0/2] Mapping an entire folio
Date: Tue, 1 Nov 2022 20:18:26 +0000 [thread overview]
Message-ID: <20221101201828.1170455-1-willy@infradead.org> (raw)
I had intended to write and test one user before sending this out,
but Dave Howells says he has a user now that wants this functionality,
so here we go. It is only compile tested.
Earlier thread on this: https://lore.kernel.org/all/YvvdFrtiW33UOkGr@casper.infradead.org/
v2:
- Remove spurious blank line change in highmem.h (David Howells)
- Insert missing "else" in folio_unmap_local() (Hyeonggon Yoo)
- Use vm_unmap_ram() instead of vunmap() in folio_unmap_local() (Hyeonggon Yoo)
- Factor vmap_alloc() out of vm_map_ram() (Uladzislau Rezki)
Matthew Wilcox (Oracle) (2):
vmalloc: Factor vmap_alloc() out of vm_map_ram()
mm: Add folio_map_local()
include/linux/highmem.h | 40 ++++++++++++++++++++++
include/linux/vmalloc.h | 6 ++--
mm/vmalloc.c | 73 +++++++++++++++++++++++++++++++----------
3 files changed, 99 insertions(+), 20 deletions(-)
--
2.35.1
next reply other threads:[~2022-11-01 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 20:18 Matthew Wilcox (Oracle) [this message]
2022-11-01 20:18 ` [PATCH v2 1/2] vmalloc: Factor vmap_alloc() out of vm_map_ram() Matthew Wilcox (Oracle)
2022-11-02 3:46 ` Hyeonggon Yoo
2022-11-02 3:59 ` Hyeonggon Yoo
2022-11-02 9:10 ` Christoph Hellwig
2022-11-01 20:18 ` [PATCH v2 2/2] mm: Add folio_map_local() Matthew Wilcox (Oracle)
2022-11-02 9:13 ` Christoph Hellwig
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=20221101201828.1170455-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
/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).