xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
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>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	Juergen Gross <juergen.gross@ts.fujitsu.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-Devel <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>,
	Matt Wilson <msw@amazon.com>
Subject: Re: [PATCH 04 of 11 v4] xen: sched_credit: let the scheduler know about node-affinity
Date: Mon, 18 Mar 2013 13:58:55 +0000	[thread overview]
Message-ID: <51471D9F.3070707@eu.citrix.com> (raw)
In-Reply-To: <9b35836856e2d1fe9adf.1363314646@hit-nxdomain.opendns.com>

On 15/03/13 02:30, Dario Faggioli wrote:
> As vcpu-affinity tells where VCPUs must run, node-affinity tells
> where they prefer to. While respecting vcpu-affinity remains mandatory,
> node-affinity is not that strict, it only expresses a preference,
> although honouring it will bring significant performance benefits
> (especially as compared to not having any affinity at all).
>
> This change modifies the VCPUs load balancing algorithm (for the
> credit scheduler only), introducing a two steps logic. During the
> first step, we use both the vcpu-affinity and the node-affinity
> masks (by looking at their intersection). The aim is giving precedence
> to the PCPUs where the domain prefers to run, as expressed by its
> node-affinity (with the intersection with the vcpu-afinity being
> necessary in order to avoid running a VCPU where it never should).
> If that fails in finding a valid PCPU, the node-affinity is just
> ignored and, in the second step, we fall back to using cpu-affinity
> only.
>
> Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> Acked-by: Juergen Gross <juergen.gross@ts.fujitsu.com>

Acked-by: George Dunlap <george.dunlap@eu.citrix.com>

  reply	other threads:[~2013-03-18 13:58 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 [this message]
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=51471D9F.3070707@eu.citrix.com \
    --to=george.dunlap@eu.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=dario.faggioli@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --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).