From: Dario Faggioli <dario.faggioli@citrix.com>
To: Elena Ufimtseva <elena.ufimtseva@oracle.com>
Cc: george.dunlap@eu.citrix.com,
George Dunlap <george.dunlap@citrix.com>,
xen-devel@lists.xen.org, joao.m.martins@oracle.com,
boris.ostrovsky@oracle.com
Subject: Re: schedulers and topology exposing questions
Date: Tue, 2 Feb 2016 12:58:28 +0100 [thread overview]
Message-ID: <1454414308.9227.102.camel@citrix.com> (raw)
In-Reply-To: <20160129215938.GD18627@elena.ufimtseva>
[-- Attachment #1.1: Type: text/plain, Size: 1216 bytes --]
On Fri, 2016-01-29 at 16:59 -0500, Elena Ufimtseva wrote:
>
> Hey Dario
>
> Please disregard the previous email with topology information.
> It was incorrect and I am attaching the topology that is actually
> result
> of Joao smt patches application.
>
Ok :-)
Well, this:
...
physical id : 0
siblings : 16
core id : 0
cpu cores : 8
...
physical id : 0
siblings : 16
core id : 0
cpu cores : 8
...
physical id : 0
siblings : 16
core id : 1
cpu cores : 8
...
[etc]
And this:
cat /proc/sys/kernel/sched_domain/cpu*/domain*/names
SMT
MC
SMT
MC
SMT
MC
SMT
MC
[etc]
Makes me think that the patch are doing their job, and that the OS is
correctly seeing a multicore, SMT-enabled topology.
Good work on that! ;-)
Thanks and Regards,
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
next prev parent reply other threads:[~2016-02-02 11:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 16:54 schedulers and topology exposing questions Elena Ufimtseva
2016-01-22 17:29 ` Dario Faggioli
2016-01-22 23:58 ` Elena Ufimtseva
2016-01-26 11:21 ` George Dunlap
2016-01-27 14:25 ` Dario Faggioli
2016-01-27 14:33 ` Konrad Rzeszutek Wilk
2016-01-27 15:10 ` George Dunlap
2016-01-27 15:27 ` Konrad Rzeszutek Wilk
2016-01-27 15:53 ` George Dunlap
2016-01-27 16:12 ` Konrad Rzeszutek Wilk
2016-01-28 9:55 ` Dario Faggioli
2016-01-29 21:59 ` Elena Ufimtseva
2016-02-02 11:58 ` Dario Faggioli [this message]
2016-01-27 16:03 ` Elena Ufimtseva
2016-01-28 9:46 ` Dario Faggioli
2016-01-29 16:09 ` Elena Ufimtseva
2016-01-28 15:10 ` Dario Faggioli
2016-01-29 3:27 ` Konrad Rzeszutek Wilk
2016-02-02 11:45 ` Dario Faggioli
2016-02-03 18:05 ` Konrad Rzeszutek Wilk
2016-01-27 14:01 ` Dario Faggioli
2016-01-28 18:51 ` Elena Ufimtseva
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=1454414308.9227.102.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=george.dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=joao.m.martins@oracle.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).