From: Dario Faggioli <dario.faggioli@citrix.com>
To: Xen-Devel <xen-devel@lists.xen.org>
Cc: Marcus Granado <Marcus.Granado@eu.citrix.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Anil Madhavapeddy <anil@recoil.org>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Matt Wilson <msw@amazon.com>
Subject: Re: [PATCH 10 of 11 v4] xl: add node-affinity to the output of `xl list`
Date: Fri, 15 Mar 2013 04:03:52 +0100 [thread overview]
Message-ID: <1363316632.3065.137.camel@Solace> (raw)
In-Reply-To: <0197084457098065914d.1363314652@hit-nxdomain.opendns.com>
[-- Attachment #1.1: Type: text/plain, Size: 3223 bytes --]
On ven, 2013-03-15 at 03:30 +0100, Dario Faggioli wrote:
> Node-affinity is now something that is under (some) control of the
> user, so show it upon request as part of the output of `xl list'
> by the `-n' option.
>
> Re the patch, the print_bitmap() related hunk is _mostly_ code motion,
> although there is a very minor change in the code, basically to allow
> using the function for printing both cpu and node bitmaps (as, in case
> all bits are sets, it used to print "any cpu", which doesn't fit the
> nodemap case).
>
For the records, this is how the output of various invocations of `xl
list ...', with different set of parameters looks like after this
change:
root@Zhaman:~# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 375 16 r----- 225.1
vm1 1 960 2 -b---- 34.0
root@Zhaman:~# xl list -Z
Name ID Mem VCPUs State Time(s) Security Label
Domain-0 0 375 16 r----- 225.4 -
vm1 1 960 2 -b---- 34.0 -
root@Zhaman:~# xl list -v
Name ID Mem VCPUs State Time(s) UUID Reason-Code Security Label
Domain-0 0 375 16 r----- 226.6 00000000-0000-0000-0000-000000000000 - -
vm1 1 960 2 -b---- 34.2 e36429cc-d2a2-4da7-b21d-b053f725e7a7 - -
root@Zhaman:~# xl list -n
Name ID Mem VCPUs State Time(s) NODE Affinity
Domain-0 0 375 16 r----- 226.8 any node
vm1 1 960 2 -b---- 34.2 0
root@Zhaman:~# xl list -nZ
Name ID Mem VCPUs State Time(s) Security Label NODE Affinity
Domain-0 0 375 16 r----- 226.9 - any node
vm1 1 960 2 -b---- 34.2 - 0
root@Zhaman:~# xl list -nv
Name ID Mem VCPUs State Time(s) UUID Reason-Code Security Label NODE Affinity
Domain-0 0 375 16 r----- 227.0 00000000-0000-0000-0000-000000000000 - - any node
vm1 1 960 2 -b---- 34.2 e36429cc-d2a2-4da7-b21d-b053f725e7a7 - - 0
(the same thing should be available here: http://pastebin.com/68kUuwyE )
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-03-15 3:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 2:30 [PATCH 00 of 11 v4] NUMA aware credit scheduling Dario Faggioli
2013-03-15 2:30 ` [PATCH 01 of 11 v4] xen, libxc: rename xenctl_cpumap to xenctl_bitmap Dario Faggioli
2013-03-15 2:30 ` [PATCH 02 of 11 v4] xen, libxc: introduce xc_nodemap_t Dario Faggioli
2013-03-15 2:30 ` [PATCH 03 of 11 v4] xen: sched_credit: when picking, make sure we get an idle one, if any Dario Faggioli
2013-03-15 8:14 ` Jan Beulich
2013-03-15 10:37 ` Dario Faggioli
2013-03-15 10:55 ` Jan Beulich
2013-03-18 14:02 ` George Dunlap
2013-03-18 14:23 ` Dario Faggioli
2013-03-15 2:30 ` [PATCH 04 of 11 v4] xen: sched_credit: let the scheduler know about node-affinity Dario Faggioli
2013-03-18 13:58 ` George Dunlap
2013-03-15 2:30 ` [PATCH 05 of 11 v4] xen: allow for explicitly specifying node-affinity Dario Faggioli
2013-03-15 8:17 ` Jan Beulich
2013-03-15 14:20 ` Daniel De Graaf
2013-03-16 7:11 ` Dario Faggioli
2013-03-15 2:30 ` [PATCH 06 of 11 v4] libxc: " Dario Faggioli
2013-03-15 2:30 ` [PATCH 07 of 11 v4] libxl: " Dario Faggioli
2013-03-18 14:33 ` Ian Campbell
2013-03-18 14:35 ` Dario Faggioli
2013-03-15 2:30 ` [PATCH 08 of 11 v4] libxl: optimize the calculation of how many VCPUs can run on a candidate Dario Faggioli
2013-03-18 14:34 ` Ian Campbell
2013-03-15 2:30 ` [PATCH 09 of 11 v4] libxl: automatic placement deals with node-affinity Dario Faggioli
2013-03-18 14:36 ` Ian Campbell
2013-03-15 2:30 ` [PATCH 10 of 11 v4] xl: add node-affinity to the output of `xl list` Dario Faggioli
2013-03-15 3:03 ` Dario Faggioli [this message]
2013-03-18 14:06 ` George Dunlap
2013-03-18 14:21 ` Dario Faggioli
2013-03-18 14:13 ` Ian Campbell
2013-03-18 14:22 ` Dario Faggioli
2013-03-15 2:30 ` [PATCH 11 of 11 v4] docs: rearrange and update NUMA placement documentation 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=1363316632.3065.137.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Marcus.Granado@eu.citrix.com \
--cc=anil@recoil.org \
--cc=dan.magenheimer@oracle.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=george.dunlap@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xen.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).