From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Justin T. Weaver" <jtweaver@hawaii.edu>
Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xen.org, henric@hawaii.edu
Subject: Re: [PATCH v3 0/4] sched: credit2: introduce per-vcpu hard and soft affinity
Date: Thu, 17 Sep 2015 17:15:13 +0200 [thread overview]
Message-ID: <1442502913.15327.100.camel@citrix.com> (raw)
In-Reply-To: <1442500040.15327.87.camel@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1676 bytes --]
On Thu, 2015-09-17 at 16:27 +0200, Dario Faggioli wrote:
> Nice. Just to be sure, is my understending of the columns label
> accurate?
> - 'No affinity' == no hard nor soft affinity for any VM
> - 'Pinning' == hard affinity used to pin VMs to NUMA nodes
> (evenly, I guess?); soft affinity untouched
> - 'NUMA scheduling' == soft affinity used to associate VMs to NUMA
> nodes (evenly, I guess?); hard affinity
> untouched
>
> Also, can you confirm that all the hard and soft affinity setting were
> done at VM creation time, i.e., they were effectively influencing where
> the memory of the VMs was being allocated? (It looks like so, from the
> number, but I wanted to be sure...)
>
BTW, just to be clear, I'm actually reviewing v4 of this series... I'm
not re-reviewing v3. :-D
However, in the process of doing so, I was looking back at previous
submissions as well, I found this and decided it was worthwhile to ask.
I know that these measurements were done on v3 and are not valid for v4
(because that version misses, and that is intentional, some of the soft
affinity bits). Still, I think it is important to keep these numbers in
mind, as they provide (at least part of) the justification for doing the
whole hard and soft affinity work, and hence I asked for the
clarifications.
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-09-17 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 9:48 [PATCH v3 0/4] sched: credit2: introduce per-vcpu hard and soft affinity Justin T. Weaver
2015-03-26 9:48 ` [PATCH v3 1/4] sched: credit2: respect per-vcpu hard affinity Justin T. Weaver
2015-03-31 14:37 ` George Dunlap
2015-03-31 17:14 ` Dario Faggioli
2015-03-31 17:32 ` George Dunlap
2015-04-23 16:00 ` Dario Faggioli
2015-05-06 12:39 ` Dario Faggioli
2015-03-26 9:48 ` [PATCH v3 2/4] sched: factor out per-vcpu affinity related code to common header file Justin T. Weaver
2015-04-23 15:22 ` Dario Faggioli
2015-03-26 9:48 ` [PATCH v3 3/4] sched: credit2: indent code sections to make review of patch 4/4 easier Justin T. Weaver
2015-04-23 15:35 ` Dario Faggioli
2015-03-26 9:48 ` [PATCH v3 4/4] sched: credit2: consider per-vcpu soft affinity Justin T. Weaver
2015-03-31 17:38 ` George Dunlap
2015-04-20 15:38 ` George Dunlap
2015-04-22 16:16 ` George Dunlap
2015-09-17 14:27 ` [PATCH v3 0/4] sched: credit2: introduce per-vcpu hard and " Dario Faggioli
2015-09-17 15:15 ` Dario Faggioli [this message]
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=1442502913.15327.100.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=henric@hawaii.edu \
--cc=jtweaver@hawaii.edu \
--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 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.