From: Ryan Harper <ryanh@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] xend: move pincpu op before memory op again
Date: Thu, 8 Dec 2005 11:46:21 -0600 [thread overview]
Message-ID: <20051208174621.GS14377@us.ibm.com> (raw)
Looks like someone merged and moved the pincpu operation to after the
memory reservation and didn't read the comments I left in the code:
# repin domain vcpus if a restricted cpus list is provided
# this is done prior to memory allocation to aide in memory
# distribution for NUMA systems.
This patch moves the pincpu op back to where it was.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
diffstat output:
XendDomainInfo.py | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
---
diff -r 5f574f9cb4bd tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py Wed Dec 7 11:57:26 2005
+++ b/tools/python/xen/xend/XendDomainInfo.py Thu Dec 8 11:42:26 2005
@@ -1165,11 +1165,6 @@
xc.domain_setcpuweight(self.domid, self.info['cpu_weight'])
- m = self.image.getDomainMemory(self.info['memory'] * 1024)
- balloon.free(m)
- xc.domain_setmaxmem(self.domid, m)
- xc.domain_memory_increase_reservation(self.domid, m, 0, 0)
-
# repin domain vcpus if a restricted cpus list is provided
# this is done prior to memory allocation to aide in memory
# distribution for NUMA systems.
@@ -1179,6 +1174,11 @@
# pincpu takes a list of ints
cpu = [ int( cpus[v % len(cpus)] ) ]
xc.domain_pincpu(self.domid, v, cpu)
+
+ m = self.image.getDomainMemory(self.info['memory'] * 1024)
+ balloon.free(m)
+ xc.domain_setmaxmem(self.domid, m)
+ xc.domain_memory_increase_reservation(self.domid, m, 0, 0)
self.createChannels()
next reply other threads:[~2005-12-08 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 17:46 Ryan Harper [this message]
2005-12-08 18:18 ` [PATCH] xend: move pincpu op before memory op again Ewan Mellor
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=20051208174621.GS14377@us.ibm.com \
--to=ryanh@us.ibm.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.