From: Peter Xu <peterx@redhat.com>
To: 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: Thu, 13 Apr 2023 11:36:37 -0400 [thread overview]
Message-ID: <ZDghhTH2KtCeAwcZ@x1n> (raw)
In-Reply-To: <3059388f-1604-c326-c66f-c2e0f9bb6cbf@redhat.com>
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!
--
Peter Xu
next prev parent reply other threads:[~2023-04-13 15:37 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 [this message]
2023-06-06 20:15 ` Vlastimil Babka
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=ZDghhTH2KtCeAwcZ@x1n \
--to=peterx@redhat.com \
--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=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).