From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: Strange interdependace between domains Date: Thu, 20 Feb 2014 07:07:44 +0100 Message-ID: <53059BB0.1000705@ts.fujitsu.com> References: <1646915994.20140213165604@gmail.com> <1392313015.32038.112.camel@Solace> <295276356.20140213222507@gmail.com> <6010385428.20140214120238@gmail.com> <1392398466.32038.334.camel@Solace> <752791084.20140217124616@gmail.com> <1392742549.32038.580.camel@Solace> <53039F55.3030901@terremark.com> <1392746781.32038.594.camel@Solace> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1392746781.32038.594.camel@Solace> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dario Faggioli Cc: Ian Campbell , Andrew Cooper , Don Slutz , xen-devel@lists.xen.org, Simon Martin , Nate Studer List-Id: xen-devel@lists.xenproject.org On 18.02.2014 19:06, Dario Faggioli wrote: > On mar, 2014-02-18 at 12:58 -0500, Don Slutz wrote: >>>> root@smartin-xen:~# xl cpupool-list -c >>>> Name CPU list >>>> Pool-0 0,1,2 >> >> Change to something like: >> >> >> Pool-0 0,1,2 (and part of 3) >> > This would be cool, and I personally would be all for it... but it > perhaps will not be that clear at pointing the user to think to > hyperthreading. :-P > >> Or add: >> >> Warning: cpupool's share hyperthreaded cpus. >> > 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). > > Also, we are certainly not talking about hot paths. > > Juergen? 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. 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. 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