From mboxrd@z Thu Jan  1 00:00:00 1970
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
Subject: Re: Strange interdependace between domains
Date: Mon, 24 Feb 2014 10:25:28 +0100
Message-ID: <530B1008.3090403@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>
	<53059BB0.1000705@ts.fujitsu.com>
	<1392920545.32038.826.camel@Solace>
	<5306F2A9.1040503@ts.fujitsu.com>
	<1393003446.32038.832.camel@Solace>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1393003446.32038.832.camel@Solace>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
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>
List-Id: xen-devel@lists.xenproject.org

On 21.02.2014 18:24, Dario Faggioli wrote:
> On ven, 2014-02-21 at 07:31 +0100, Juergen Gross wrote:
>> On 20.02.2014 19:22, Dario Faggioli wrote:
>>> 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?
>>
> Looks reasonable.

Another solution would be to add a --long option. This would have the advantage
of not having to choose between clobbering the table output or not being able
to show multiple optional information items.

So we could do something like:

# xl cpupool-list --long
Pool-0
   n-cpus:        1
   cpu-list:      0
   scheduler:     credit
   n-domains:     1
   domain-list:   Dom0
   res-share-lvl: core
   res-sharers:   lw_pool
lw_pool
   n-cpus:        1
   cpu-list:      1
   scheduler:     credit
   n-domains:     0
   domain-list:
   res-share-lvl: core
   res-sharers:   Pool-0
bs2_pool
   n-cpus:        2
   cpu-list:      2,3
   scheduler:     credit
   n-domains:     1
   domain-list:   BS2000
   res-share-lvl: socket
   res-sharers:   Pool-0,lw_pool

We could add scheduler parameters, NUMA-information, ... as well.


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