xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0/5] xl: allow for node-wise specification of vcpu pinning
Date: Mon, 16 Sep 2013 20:40:36 +0200	[thread overview]
Message-ID: <20130916183518.20003.61823.stgit@hit-nxdomain.opendns.com> (raw)

Hi all,

Take 3 of this series. It allows for specifying vcpu pinning taking NUMA nodes
into account. IOW, something like this:

 * "nodes:0-3": all pCPUs of nodes 0,1,2,3;
 * "nodes:0-3,^node:2": all pCPUS of nodes 0,1,3;
 * "1,nodes:1-2,^6": pCPU 1 plus all pCPUs of nodes 1,2
   but not pCPU 6;

All comments that v2 got have been addressed. In particular, the test script
has been rearranged and enhanced to match the requested behavior (generate a
test vector file and then read it).

Thanks and Regards,
Dario

---
 '* = Acked

Dario Faggioli (5):
    * xl: update the manpage about "cpus=" and NUMA node-affinity
    * libxl: introduce libxl_node_to_cpumap
      xl: allow for node-wise specification of vcpu pinning
    * xl: implement and enable dryrun mode for `xl vcpu-pin'
      xl: test script for the cpumap parser (for vCPU pinning)


 docs/man/xl.cfg.pod.5                           |   42 +++
 tools/libxl/check-xl-vcpupin-parse              |  294 +++++++++++++++++++++++
 tools/libxl/check-xl-vcpupin-parse.data-example |   53 ++++
 tools/libxl/libxl_utils.c                       |   22 ++
 tools/libxl/libxl_utils.h                       |    3 
 tools/libxl/xl_cmdimpl.c                        |  191 +++++++++++----
 tools/libxl/xl_cmdtable.c                       |    2 
 7 files changed, 544 insertions(+), 63 deletions(-)
 create mode 100755 tools/libxl/check-xl-vcpupin-parse
 create mode 100644 tools/libxl/check-xl-vcpupin-parse.data-example

--
<<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)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2013-09-16 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 18:40 Dario Faggioli [this message]
2013-09-16 18:40 ` [PATCH 1/5] xl: update the manpage about "cpus=" and NUMA node-affinity Dario Faggioli
2013-09-16 18:40 ` [PATCH 2/5] libxl: introduce libxl_node_to_cpumap Dario Faggioli
2013-09-16 18:41 ` [PATCH 3/5] xl: allow for node-wise specification of vcpu pinning Dario Faggioli
2013-09-16 18:41 ` [PATCH 4/5] xl: implement and enable dryrun mode for `xl vcpu-pin' Dario Faggioli
2013-09-16 18:41 ` [PATCH 5/5] xl: test script for the cpumap parser (for vCPU pinning) Dario Faggioli
2013-09-16 18:47 ` [PATCH 0/5] xl: allow for node-wise specification of vcpu pinning Dario Faggioli
2013-09-25 11:03   ` Dario Faggioli
2013-11-05 17:24     ` George Dunlap
2013-11-05 22:33       ` 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=20130916183518.20003.61823.stgit@hit-nxdomain.opendns.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.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).