Skip to content

Conversation

@edwintorok
Copy link
Contributor

This partially applies the following commit to reduce the complexity of a Xen-4.20 patch:

xenopsd-xc: do not try keep track of free memory when planning NUMA nodes (CA-411684)

Free memory is now properly accounted for because the memory pages are claimed
within the NUMA mutex, so there's no need to have double tracking.

On top of that, this code never increased the free memory, which means that it
always reached a point where it was impossible to allocate a domain into a
single numa node.
Signed-off-by: Pau Ruiz Safont [email protected]

However it doesn't actually drop the free memory accounting code, so: No functional change

This partially applies the following commit to reduce the complexity of a
Xen-4.20 patch:

> xenopsd-xc: do not try keep track of free memory when planning NUMA nodes (CA-411684)
>
> Free memory is now properly accounted for because the memory pages are claimed
> within the NUMA mutex, so there's no need to have double tracking.
>
> On top of that, this code never increased the free memory, which means that it
> always reached a point where it was impossible to allocate a domain into a
> single numa node.
> Signed-off-by: Pau Ruiz Safont <[email protected]>

However it doesn't actually drop the free memory accounting code, so:
No functional change

Signed-off-by: Edwin Török <[email protected]>
@edwintorok edwintorok requested a review from mg12 November 27, 2025 15:49
@edwintorok
Copy link
Contributor Author

There is also a spec change to go with this for Xen-4.20 that updates the patch, I've linked this PR from that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants