From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
keir@xen.org, xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/2] Credit2: fix per-socket runqueue setup
Date: Mon, 1 Sep 2014 14:59:23 +0100 [thread overview]
Message-ID: <54047BBB.3050507@eu.citrix.com> (raw)
In-Reply-To: <53FB1088020000780002D105@mail.emea.novell.com>
On 08/25/2014 09:31 AM, Jan Beulich wrote:
>>>> On 22.08.14 at 19:15, <dario.faggioli@citrix.com> wrote:
>> root@tg03:~# xl dmesg |grep -i runqueue
>> (XEN) Adding cpu 0 to runqueue 1
>> (XEN) First cpu on runqueue, activating
>> (XEN) Adding cpu 1 to runqueue 1
>> (XEN) Adding cpu 2 to runqueue 1
>> (XEN) Adding cpu 3 to runqueue 1
>> (XEN) Adding cpu 4 to runqueue 1
>> (XEN) Adding cpu 5 to runqueue 1
>> (XEN) Adding cpu 6 to runqueue 1
>> (XEN) Adding cpu 7 to runqueue 1
>> (XEN) Adding cpu 8 to runqueue 1
>> (XEN) Adding cpu 9 to runqueue 1
>> (XEN) Adding cpu 10 to runqueue 1
>> (XEN) Adding cpu 11 to runqueue 1
>> (XEN) Adding cpu 12 to runqueue 0
>> (XEN) First cpu on runqueue, activating
>> (XEN) Adding cpu 13 to runqueue 0
>> (XEN) Adding cpu 14 to runqueue 0
>> (XEN) Adding cpu 15 to runqueue 0
>> (XEN) Adding cpu 16 to runqueue 0
>> (XEN) Adding cpu 17 to runqueue 0
>> (XEN) Adding cpu 18 to runqueue 0
>> (XEN) Adding cpu 19 to runqueue 0
>> (XEN) Adding cpu 20 to runqueue 0
>> (XEN) Adding cpu 21 to runqueue 0
>> (XEN) Adding cpu 22 to runqueue 0
>> (XEN) Adding cpu 23 to runqueue 0
>>
>> Which makes a lot more sense. :-)
> But it looks suspicious that the low numbered CPUs get assigned to
> runqueue 1. Is there an explanation for this, or are surprises to be
> expected on larger than dual-socket systems?
Well the explanation is most likely from the cpu_topology info from the
cover letter (0/2): On his machine, cpus 0-11 are on socket 1, and cpus
12-23 are on socket 0. Why that's the topology reported (I presume in
ACPI?) I'm not sure.
-George
next prev parent reply other threads:[~2014-09-01 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 17:15 [PATCH 0/2] Credit2: fix per-socket runqueue setup Dario Faggioli
2014-08-22 17:15 ` [PATCH 1/2] x86: during boot, anticipate identifying the boot cpu Dario Faggioli
2014-08-22 17:28 ` Andrew Cooper
2014-08-22 18:40 ` Dario Faggioli
2014-08-25 8:35 ` Jan Beulich
2014-08-25 8:39 ` Jan Beulich
2014-09-01 15:12 ` George Dunlap
2014-09-01 15:24 ` Jan Beulich
2014-08-22 17:15 ` [PATCH 2/2] sched: credit2: use boot CPU info for CPU #0 Dario Faggioli
2014-08-25 8:41 ` Jan Beulich
2014-08-25 8:31 ` [PATCH 0/2] Credit2: fix per-socket runqueue setup Jan Beulich
2014-09-01 13:59 ` George Dunlap [this message]
2014-09-02 16:46 ` Dario Faggioli
2014-09-03 10:00 ` George Dunlap
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=54047BBB.3050507@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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.