xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: [PATCH 00 of 11 v4] NUMA aware credit scheduling
Date: Fri, 15 Mar 2013 03:30:42 +0100	[thread overview]
Message-ID: <patchbomb.1363314642@hit-nxdomain.opendns.com> (raw)

Hello,

Round 4 of the NUMA aware scheduling series. Very few going on, actually, as
the comments to v3 where not a big deal... Nevertheless, I, as usual, really
appreciated them a lot, and I think I've addressed them all. The only notable
change is on patch 05/11, where I discovered a small but nasty bug (see the
specific changelog).

I couldn't rerun the full set of my usual benchmarks, but I really don't think
that to be necessary, as practically no functional change is being introduced,
wrt to v3. However, I did run a couple of them, randomly, just to be sure,
and the numbers actually do look almost identical to these ones:

 http://lists.xen.org/archives/html/xen-devel/2013-02/msg00009.html

What I'm now missing is a couple of Ack-s from the relevant people. In fact,
almost all the patches carry more than one Ack, but there are a few of them
which are missing Ack-s from the actual maintainers of the code they touch.
In some more details, and with
  '*'='properly Ack-ed',
  '+'= 'Ack-ed but _not_ by the maintainer',
here it comes the series:

 * 01/11 xen, libxc: rename xenctl_cpumap to xenctl_bitmap
 * 02/11 xen, libxc: introduce xc_nodemap_t
 * 03/11 xen: sched_credit: when picking, make sure we get an idle one, if any
 + 04/11 xen: sched_credit: let the scheduler know about node-affinity
 * 05/11 xen: allow for explicitly specifying node-affinity
 * 06/11 libxc: allow for explicitly specifying node-affinity
 + 07/11 libxl: allow for explicitly specifying node-affinity
 + 08/11 libxl: optimize the calculation of how many VCPUs can run on a candidate
 + 09/11 libxl: automatic placement deals with node-affinity
 + 10/11 xl: add node-affinity to the output of `xl list
 * 11/11 docs: rearrange and update NUMA placement documentation

So, George, if, as you said, you're fine with it, could you explicitly
ack 04/11 ?
Also, IanC and IanJ, could you have a look and ack (if you feel like
so, of course) 07/11, 08/11, 09/11 and 10/11 ?

Thanks a lot and Regads,
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)

             reply	other threads:[~2013-03-15  2:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15  2:30 Dario Faggioli [this message]
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
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=patchbomb.1363314642@hit-nxdomain.opendns.com \
    --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).