From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Don Slutz <dslutz@verizon.com>,
xen-devel@lists.xen.org, Simon Martin <furryfuttock@gmail.com>,
Nate Studer <nate.studer@dornerworks.com>
Subject: Re: Strange interdependace between domains
Date: Fri, 21 Feb 2014 07:31:05 +0100 [thread overview]
Message-ID: <5306F2A9.1040503@ts.fujitsu.com> (raw)
In-Reply-To: <1392920545.32038.826.camel@Solace>
On 20.02.2014 19:22, Dario Faggioli wrote:
> On gio, 2014-02-20 at 07:07 +0100, Juergen Gross wrote:
>> On 18.02.2014 19:06, Dario Faggioli wrote:
>
>>> While this one, although a bit more "boring" than the above, would
>>> probably be something quite valuable to have!
>>>
>>> I can only think of rather expensive ways of implementing it, involving
>>> going through all the cpupools and, for each cpupool, through all its
>>> cpus and check the topology relationships, but perhaps there are others
>>> (I'll think harder).
>>>
>> Adding some information like this would be nice, indeed. But I think we should
>> not limit this to just hyperthreads. There are more levels of shared resources,
>> like caches or memory interfaces on the same socket. In case we want to add
>> information about potential performance influences due to shared resources, we
>> should be more generic.
>>
> All true... To the point that I know also wonder what a suitable
> interface and a not too verbose output configuration could be...
Well, looking at the available topology information I think it should look like
the following example:
# xl cpupool-list --shareinfo
Name CPUs Sched Active Domain count shared resources
Pool-0 1 credit y 1 core: lw_pool
lw_pool 1 credit y 0 core: Pool-0
bs2_pool 2 credit y 1 socket: Pool-0,lw_pool
What do you think?
>> And what about some NUMA information? Wouldn't it be worthwhile to show memory
>> locality information as well? This should be considered to be displayed by
>> "xl list", too.
>>
> Indeed. I actually have an half backed series doing right that. It's a
> bit more complicated (still from an interface point of view), as that
> info resides in Xen, and some new hcall or similar is required to
> retrieve that.
>
> I'll post it in early 4.5 dev cycle.
Please do!
Juergen
--
Juergen Gross Principal Developer Operating Systems
PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 62060 2932
Fujitsu e-mail: juergen.gross@ts.fujitsu.com
Mies-van-der-Rohe-Str. 8 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2014-02-21 6:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 16:56 Strange interdependace between domains Simon Martin
2014-02-13 17:07 ` Ian Campbell
2014-02-13 17:28 ` Simon Martin
2014-02-13 17:39 ` Dario Faggioli
2014-02-13 17:36 ` Dario Faggioli
2014-02-13 20:47 ` Nate Studer
2014-02-13 22:25 ` Simon Martin
2014-02-13 23:13 ` Dario Faggioli
2014-02-14 10:26 ` Don Slutz
2014-02-14 12:02 ` Simon Martin
2014-02-14 13:26 ` Andrew Cooper
2014-02-14 17:21 ` Dario Faggioli
2014-02-17 12:46 ` Simon Martin
2014-02-18 16:55 ` Dario Faggioli
2014-02-18 17:58 ` Don Slutz
2014-02-18 18:06 ` Dario Faggioli
2014-02-20 6:07 ` Juergen Gross
2014-02-20 18:22 ` Dario Faggioli
2014-02-21 6:31 ` Juergen Gross [this message]
2014-02-21 17:24 ` Dario Faggioli
2014-02-24 9:25 ` Juergen Gross
2014-02-17 13:19 ` Juergen Gross
2014-02-17 15:08 ` Dario Faggioli
2014-02-18 5:31 ` Juergen Gross
2014-02-17 14:13 ` Nate Studer
2014-02-18 16:47 ` 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=5306F2A9.1040503@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=dslutz@verizon.com \
--cc=furryfuttock@gmail.com \
--cc=nate.studer@dornerworks.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 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.