From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: Re: NUMA TODO-list for xen-devel Date: Fri, 3 Aug 2012 15:42:38 -0700 (PDT) Message-ID: <45216a40-585d-47df-86a0-3b78843d7ef7@default> References: <1343837796.4958.32.camel@Solace> <501BA1C0.7040100@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <501BA1C0.7040100@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andre Przywara , Dario Faggioli Cc: Anil Madhavapeddy , George Dunlap , xen-devel , Jan Beulich , Andrew Cooper , "Zhang, Yang Z" List-Id: xen-devel@lists.xenproject.org > > [D] - Dynamic memory migration between different nodes of the host. As > > the counter-part of the NUMA-aware scheduler. > > I once read about a VMware feature: bandwith-limited migration in the > background, hot pages first. So we get flexibility and avoid CPU > starving, but still don't hog the system with memory copying. > Sounds quite ambitious, though. Something like this, but between NUMA nodes instead of physical systems? http://osnet.cs.binghamton.edu/publications/hines09postcopy_osr.pdf