From: Dario Faggioli <raistlin@linux.it>
To: xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Andre Przywara <andre.przywara@amd.com>
Subject: [PATCH 0 of 2 RFC] xl: move domeins among NUMA nodes
Date: Fri, 06 Jul 2012 11:54:03 +0200 [thread overview]
Message-ID: <patchbomb.1341568443@Solace> (raw)
Hello Everyone,
FIRST OF ALL, this is an RFC and, more important, it implements a new feature
(although it's a small one), so it is not meant for 4.2. Of course, comments
are more than welcome, if you happen to find the time to look at it (after all,
it is why I'm releasing it)... Just don't rush if you're busy with some
pressing release-related stuff! :-P
The above being stated, this series tries to tackle the problem of moving an
already existent domain from a (some) NUMA node(s) to a (some) other(s). In
fact, changing vcpu-affinity affects the node affinity of the domain itself,
but this is only effective wrt the memory that will be allocated in the future,
while all the existent pages are untouched. This of course makes a lot of
sense, but there might be the need to _fully_ move a domain, both vcpus and
memory wise, and that's what this series tries to achieve.
Just let me add that the whole process looks a lot like a suspend/resume (or
either to a local migration) to me, and that's why I implemented it like that
for now. I went for the suspend resume approach, but I think I can make it more
migration-oriented solution if wanted, as it'd reduce the downtime (although,
in that case, we'd need to have twice the memory of the domain available during
the process).
Of course, I can also add the proper logic and interface to the hypervisor, but
I'm not sure it buys that much, as there will still be something very similar
to suspension or migration, just called and used a little bit differently (but
of course I'm open to change my mind :-)).
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
next reply other threads:[~2012-07-06 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 9:54 Dario Faggioli [this message]
2012-07-06 9:54 ` [PATCH 1 of 2 RFC] xl: parse extra_config options even when restoring Dario Faggioli
2012-07-06 9:54 ` [PATCH 2 of 2 RFC] xl: allow for moving the domain's memory when changing vcpu affinity Dario Faggioli
2012-07-06 12:53 ` George Dunlap
2012-07-06 13:25 ` Ian Campbell
2012-07-06 13:30 ` George Dunlap
2012-07-06 13:38 ` Ian Campbell
2012-07-06 14:05 ` Dario Faggioli
2012-07-06 14:07 ` George Dunlap
2012-07-06 14:42 ` Ian Campbell
2012-07-06 13:57 ` Dario Faggioli
2012-07-06 14:04 ` George Dunlap
2012-07-06 14:14 ` Dario Faggioli
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=patchbomb.1341568443@Solace \
--to=raistlin@linux.it \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andre.przywara@amd.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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 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.