From: "Daniel P. Berrange" <berrange@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] (resent) NUMA node migration
Date: Fri, 21 Dec 2007 22:45:55 +0000 [thread overview]
Message-ID: <20071221224554.GG27601@redhat.com> (raw)
In-Reply-To: <476C40BE.1030907@amd.com>
On Fri, Dec 21, 2007 at 11:39:58PM +0100, Andre Przywara wrote:
> forgot my signed-off, thus resent...
>
> the following patch adds NUMA node migration based on live migration to
> xend. By adding another parameter to "xm migrate" the target NUMA node
> number gets propagated to the target host (can be both localhost or a
> remote host). The restore function then sets the VCPU affinity
> accordingly. Only changes Python code in xend. I hope that the patch
> doesn't break XenAPI compatibility (adding a parameter seems fine?).
>
> # xm migrate --live --node=<nodenr> <domid> localhost
> <nodenr> is the number as shown with 'xm info' under node_to_cpu
>
> I am aware that using live migration isn't the best approach (takes
> twice the memory and quite some time), but it's less intrusive and works
> fine (given localhost migration stability...)
>
> Feedback appreciated, especially since I speak Python since Monday...
Rather than using '-1' to indiciate no pinning, it is more common
python practice to use None, which indicates no value. Other than
that it looks reasonable
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-12-21 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 22:39 [PATCH] (resent) NUMA node migration Andre Przywara
2007-12-21 22:45 ` Daniel P. Berrange [this message]
2007-12-22 0:53 ` John Levon
2007-12-22 1:15 ` Ian Pratt
2007-12-22 9:42 ` tgh
2007-12-23 21:12 ` Mark Williamson
2008-01-09 14:35 ` Andre Przywara
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=20071221224554.GG27601@redhat.com \
--to=berrange@redhat.com \
--cc=andre.przywara@amd.com \
--cc=xen-devel@lists.xensource.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.