From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Nikolaos Karaolidis <nick@karaolidis.com>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: "Oscar Salvador" <osalvador@suse.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowangio@gmail.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Michal Hocko" <mhocko@suse.com>, "Hui Zhu" <teawater@gmail.com>,
"Georgi Djakov" <georgi.djakov@oss.qualcomm.com>,
virtualization@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH RFC 0/6] virtio-mem: support memmap_on_memory
Date: Tue, 3 Nov 2026 17:29:44 +0100 [thread overview]
Message-ID: <fd6094d5-50d3-4e73-8c09-91b0769476ab@kernel.org> (raw)
In-Reply-To: <20261103-virtio-mem-memmap-v1-0-308ae1da6240@karaolidis.com>
On 11/3/26 10:50, Nikolaos Karaolidis wrote:
> virtio-mem adds memory without MHP_MEMMAP_ON_MEMORY. With the memory
> onlined to ZONE_MOVABLE, a VM that grows to many times its boot size
> can run short of unmovable memory. I ran into this while working on
> a guest-initiated memory negotiation project.
Care to pitch the use case to me?
I'm all for making virtio-mem better suitable for some workloads, but my time is
limited.
Is this something that your use case would actually benefit from, or was that
project already discarded?
Why so much MOVABLE memory, and how do other kernel allocations (page tables
etc) cope with that?
--
Cheers,
David
next prev parent reply other threads:[~2026-11-03 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:50 Nikolaos Karaolidis
2026-11-03 9:50 ` [PATCH RFC 1/6] mm/memory_hotplug: add and export mhp_memmap_on_memory_nr_pages() Nikolaos Karaolidis
2026-11-03 9:50 ` [PATCH RFC 2/6] virtio-mem: prepare memory notifier for a self-hosted memmap Nikolaos Karaolidis
2026-11-03 9:50 ` [PATCH RFC 3/6] virtio-mem: support memmap_on_memory in Big Block Mode Nikolaos Karaolidis
2026-11-03 9:50 ` [PATCH RFC 4/6] virtio-mem: move virtio_mem_sbm_try_remove_unplugged_mb() Nikolaos Karaolidis
2026-11-03 9:50 ` [PATCH RFC 5/6] virtio-mem: support memmap_on_memory in Sub Block Mode Nikolaos Karaolidis
2026-11-03 9:50 ` [PATCH RFC 6/6] Documentation/admin-guide/mm: document virtio-mem memmap_on_memory Nikolaos Karaolidis
2026-11-03 16:29 ` David Hildenbrand (Arm) [this message]
2026-11-03 17:37 ` [PATCH RFC 0/6] virtio-mem: support memmap_on_memory Nick Karaolidis
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=fd6094d5-50d3-4e73-8c09-91b0769476ab@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=eperezma@redhat.com \
--cc=georgi.djakov@oss.qualcomm.com \
--cc=jasowangio@gmail.com \
--cc=liam@infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=mst@redhat.com \
--cc=nick@karaolidis.com \
--cc=osalvador@suse.de \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=teawater@gmail.com \
--cc=vbabka@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®