From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Michal Orzel <michal.orzel@amd.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/2] xen/mm: limit non-scrubbed allocations to a specific order
Date: Thu, 15 Jan 2026 11:48:47 +0100 [thread overview]
Message-ID: <aWjGDy3ixLRTpZbF@Mac.lan> (raw)
In-Reply-To: <b535344e-1f27-4d5c-85aa-1529868f85fc@suse.com>
On Wed, Jan 14, 2026 at 09:48:59AM +0100, Jan Beulich wrote:
> On 13.01.2026 15:01, Roger Pau Monné wrote:
> > On Fri, Jan 09, 2026 at 12:19:26PM +0100, Jan Beulich wrote:
> >> On 08.01.2026 18:55, Roger Pau Monne wrote:
> >>> --- a/xen/common/memory.c
> >>> +++ b/xen/common/memory.c
> >>> @@ -279,6 +279,18 @@ static void populate_physmap(struct memop_args *a)
> >>>
> >>> if ( unlikely(!page) )
> >>> {
> >>> + nodeid_t node = MEMF_get_node(a->memflags);
> >>> +
> >>> + if ( memory_scrub_pending(node) ||
> >>> + (node != NUMA_NO_NODE &&
> >>> + !(a->memflags & MEMF_exact_node) &&
> >>> + memory_scrub_pending(node = NUMA_NO_NODE)) )
> >>> + {
> >>> + scrub_free_pages(node);
> >>> + a->preempted = 1;
> >>> + goto out;
> >>> + }
> >>
> >> At least for order 0 requests there's no point in trying this. With the
> >> current logic, actually for orders up to MAX_DIRTY_ORDER.
> >
> > Yes, otherwise we might force the CPU to do some scrubbing work when
> > it won't satisfy it's allocation request anyway.
> >
> >> Further, from a general interface perspective, wouldn't we need to do the
> >> same for at least XENMEM_increase_reservation?
> >
> > Possibly yes. TBH I would also be fine with strictly limiting
> > XENMEM_increase_reservation to 2M order extents, even for the control
> > domain. The physmap population is the only that actually requires
> > bigger extents.
>
> Hmm, that's an option, yes, but an ABI-changing one.
I don't think it changes the ABI: Xen has always reserved the right to
block high order allocations. See for example how max_order() has
different limits depending on the domain permissions, and I would not
consider those limits part of the ABI, they can be changed from the
command line.
Thanks, Roger.
next prev parent reply other threads:[~2026-01-15 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 17:55 [PATCH 0/2] xen/mm: limit in-place scrubbing Roger Pau Monne
2026-01-08 17:55 ` [PATCH 1/2] xen/mm: add a NUMA node parameter to scrub_free_pages() Roger Pau Monne
2026-01-09 10:22 ` Jan Beulich
2026-01-09 14:46 ` Roger Pau Monné
2026-01-09 14:50 ` Jan Beulich
2026-01-08 17:55 ` [PATCH 2/2] xen/mm: limit non-scrubbed allocations to a specific order Roger Pau Monne
2026-01-09 11:19 ` Jan Beulich
2026-01-13 14:01 ` Roger Pau Monné
2026-01-14 8:48 ` Jan Beulich
2026-01-15 10:48 ` Roger Pau Monné [this message]
2026-01-15 10:56 ` Jan Beulich
2026-01-15 13:05 ` Roger Pau Monné
2026-01-09 10:15 ` [PATCH 0/2] xen/mm: limit in-place scrubbing Jan Beulich
2026-01-09 10:29 ` Andrew Cooper
2026-01-09 11:32 ` Jan Beulich
2026-01-09 11:34 ` Andrew Cooper
2026-01-09 12:31 ` Roger Pau Monné
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=aWjGDy3ixLRTpZbF@Mac.lan \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.