All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.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: Thu, 20 Feb 2014 19:22:25 +0100	[thread overview]
Message-ID: <1392920545.32038.826.camel@Solace> (raw)
In-Reply-To: <53059BB0.1000705@ts.fujitsu.com>


[-- Attachment #1.1: Type: text/plain, Size: 1716 bytes --]

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...

> 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.

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

  reply	other threads:[~2014-02-20 18:22 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 [this message]
2014-02-21  6:31                     ` Juergen Gross
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=1392920545.32038.826.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=furryfuttock@gmail.com \
    --cc=juergen.gross@ts.fujitsu.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.