From: Vlastimil Babka <vbabka@suse.cz>
To: Peter Xu <peterx@redhat.com>, David Hildenbrand <david@redhat.com>
Cc: Lokesh Gidra <lokeshgidra@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Brian Geffon <bgeffon@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Kalesh Singh <kaleshsingh@google.com>,
Nicolas Geoffray <ngeoffray@google.com>,
Jared Duke <jdduke@google.com>,
android-mm <android-mm@google.com>,
Blake Caldwell <blake.caldwell@colorado.edu>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: RFC for new feature to move pages from one vma to another without split
Date: Tue, 6 Jun 2023 22:15:38 +0200 [thread overview]
Message-ID: <6403a950-7367-0b00-8cd5-2f0a32dac953@suse.cz> (raw)
In-Reply-To: <ZDghhTH2KtCeAwcZ@x1n>
On 4/13/23 17:36, Peter Xu wrote:
> On Thu, Apr 13, 2023 at 10:10:44AM +0200, David Hildenbrand wrote:
>> So instead, we consider the whole address space as a virtual, anon file,
>> starting at offset 0. The pgoff of a VMA is then simply the offset in that
>> virtual file (easily computed from the start of the VMA), and VMA merging is
>> just the same as for an ordinary file.
>
> Interesting point, thanks!
FYI, I've advised a master thesis exploring how to update page->index during
mremap() to keep things mergeable:
https://dspace.cuni.cz/bitstream/handle/20.500.11956/176288/120426800.pdf
I think the last RFC posting was:
https://lore.kernel.org/all/20220516125405.1675-1-matenajakub@gmail.com/
It was really tricky for the general case. Maybe it would be more feasible
for the limited case Lokesh describes, if we could be sure the pages that
are moved aren't mapped anywhere else.
next prev parent reply other threads:[~2023-06-06 20:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 22:27 RFC for new feature to move pages from one vma to another without split Lokesh Gidra
2023-04-06 17:29 ` Peter Xu
2023-04-10 7:41 ` Lokesh Gidra
2023-04-11 15:14 ` Peter Xu
2023-05-08 22:56 ` Lokesh Gidra
2023-05-16 16:43 ` Peter Xu
2023-04-12 8:47 ` David Hildenbrand
2023-04-12 15:58 ` Peter Xu
2023-04-13 8:10 ` David Hildenbrand
2023-04-13 15:36 ` Peter Xu
2023-06-06 20:15 ` Vlastimil Babka [this message]
2023-06-06 23:18 ` Suren Baghdasaryan
2023-06-08 10:05 ` Lokesh Gidra
2023-09-14 15:30 ` Suren Baghdasaryan
2023-06-07 20:17 ` Lorenzo Stoakes
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=6403a950-7367-0b00-8cd5-2f0a32dac953@suse.cz \
--to=vbabka@suse.cz \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=android-mm@google.com \
--cc=axelrasmussen@google.com \
--cc=bgeffon@google.com \
--cc=blake.caldwell@colorado.edu \
--cc=david@redhat.com \
--cc=jdduke@google.com \
--cc=kaleshsingh@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=ngeoffray@google.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=surenb@google.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).