From: Don Morris <don.morris@hp.com>
To: Cody P Schafer <cody@linux.vnet.ibm.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
David Hansen <dave@linux.vnet.ibm.com>
Subject: Re: [LSF/MM TOPIC][ATTEND] Handling NUMA layout changes at runtime
Date: Fri, 22 Feb 2013 09:23:22 -0500 [thread overview]
Message-ID: <51277F5A.9080807@hp.com> (raw)
In-Reply-To: <20130221194733.GA3778@negative>
On 02/21/2013 02:47 PM, Cody P Schafer wrote:
> Yes, this is late. Sorry.
>
> I'd like to discuss the following topic:
I'd be interested in discussing this as well (no code at the moment,
but I at the least I could contribute experiences on how the HP-UX
memory management system handles this if invited).
Thanks,
Don Morris
>
> --
>
> Presently, NUMA layout is determined at boot time and never changes again.
> This setup works for real hardware, but virtual machines are more dynamic:
> they could be migrated between different hosts, and have to share the physical
> memory space with other VMs which are also being moved around or shut down
> while other new VMs are started up. As a result, the physical backing memory
> that a VM had when it started up changes at runtime.
>
> Problems to be overcome:
>
> - How should userspace be notified? Do we need new interfaces so
> applications can query memory to see if it was affected?
>
> - Can we make the NUMA layout initialization generic? This also
> implies that all initialization of struct zone/struct
> page/NODE_DATA() would be made (somewhat) generic.
>
> - Some one-time allocations now will know they are on a non-optimal
> node.
>
> - hotpluged per node data is (in general) not being allocated optimally)
>
> - NODE_DATA() for hotpluged nodes is allocated off-node (except for
> ia64).
>
> - SLUB's kmem_cache_node is always allocated off-node for
> hotpluged nodes.
>
> [Not a new problem, but one that needs solving].
>
> Some more generic NUMA layout/mm init things:
>
> - boot-time and hotplug NUMA init don't share enough code.
>
> - architectures do not share mm init code
>
> - NUMA layout (from init) is kept (if it is kept at all) in only arch
> specific ways. Memblock _happens_ to contain this info, while also
> also tracking allocations, and every arch but powerpc discards it as
> __init/__initdata)
>
> A WIP patchset addressing initial reconfiguration of the page allocator:
> https://github.com/jmesmon/linux/tree/dnuma/v25
>
> --
> Cody P Schafer
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
> .
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-02-22 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 19:47 [LSF/MM TOPIC][ATTEND] Handling NUMA layout changes at runtime Cody P Schafer
2013-02-22 14:23 ` Don Morris [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=51277F5A.9080807@hp.com \
--to=don.morris@hp.com \
--cc=cody@linux.vnet.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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 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).