From: David Hildenbrand <david@redhat.com>
To: Gregory Price <gourry@gourry.net>
Cc: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-mm@kvack.org, linux-cxl@vger.kernel.org,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Ira Weiny" <ira.weiny@intel.com>,
"John Groves" <John@groves.net>,
virtualization@lists.linux.dev,
"Oscar Salvador" <osalvador@suse.de>,
qemu-devel@nongnu.org, "Dave Jiang" <dave.jiang@intel.com>,
"Dan Williams" <dan.j.williams@intel.com>,
linuxarm@huawei.com, wangkefeng.wang@huawei.com,
"John Groves" <jgroves@micron.com>, "Fan Ni" <fan.ni@samsung.com>,
"Navneet Singh" <navneet.singh@intel.com>,
"“Michael S. Tsirkin”" <mst@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [RFC] Virtualizing tagged disaggregated memory capacity (app specific, multi host shared)
Date: Tue, 22 Oct 2024 16:35:30 +0200 [thread overview]
Message-ID: <4a14d90b-75f0-4f4f-9e04-e2f7a39d85ba@redhat.com> (raw)
In-Reply-To: <Zxe1h8-E-OcO9cG3@PC2K9PVX.TheFacebook.com>
On 22.10.24 16:24, Gregory Price wrote:
> On Tue, Oct 22, 2024 at 11:33:07AM +0200, David Hildenbrand wrote:
>> On 20.09.24 11:06, Gregory Price wrote:
>>
>>> The only concern is when insufficient ZONE_NORMAL exists to support
>>> ZONE_MOVABLE capacity - but this is unlikely to be the general scenario AND
>>> can be mitigated w/ existing mechanisms.
>>
>> It might be worthwhile looking at
>> Documentation/admin-guide/mm/memory-hotplug.rst "auto-movable" memory
>> onlining polciy. It might not fit all sue cases, though (just like
>> ZONE_MOVABLE doesn't)
>>
>
> I managed to miss auto-movable in my last pass through there. Though for
> our use-case, forcibly preventing ZONE_NORMAL for all CXL is the preferred
> option in an effort to keep as much kernel resources out of high latency
> memory.
Yes, that makes sense for this memory with very different performance
characteristics.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-10-22 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 16:22 [RFC] Virtualizing tagged disaggregated memory capacity (app specific, multi host shared) Jonathan Cameron via
2024-08-16 7:05 ` Hannes Reinecke
2024-08-16 9:41 ` Jonathan Cameron via
2024-08-19 2:12 ` John Groves
2024-08-19 15:40 ` Jonathan Cameron via
2024-09-17 19:37 ` Jonathan Cameron via
2024-10-22 14:11 ` Gregory Price
2024-09-17 19:56 ` Jonathan Cameron via
2024-09-18 12:12 ` Jonathan Cameron
2024-09-19 9:09 ` David Hildenbrand
2024-09-20 9:06 ` Gregory Price
2024-10-22 9:33 ` David Hildenbrand
2024-10-22 14:24 ` Gregory Price
2024-10-22 14:35 ` David Hildenbrand [this message]
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=4a14d90b-75f0-4f4f-9e04-e2f7a39d85ba@redhat.com \
--to=david@redhat.com \
--cc=John@groves.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=gourry@gourry.net \
--cc=imammedo@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jgroves@micron.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=navneet.singh@intel.com \
--cc=osalvador@suse.de \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux.dev \
--cc=wangkefeng.wang@huawei.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).