All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Re: [Patch] support of cpu pools in xl
Date: Mon, 20 Sep 2010 06:58:54 +0200	[thread overview]
Message-ID: <4C96EA0E.7090105@ts.fujitsu.com> (raw)
In-Reply-To: <1284748120.15518.246.camel@localhost.localdomain>

On 09/17/10 20:28, Ian Campbell wrote:
> On Fri, 2010-09-17 at 16:53 +0100, Ian Jackson wrote:
>> Ian Campbell writes ("Re: [Xen-devel] Re: [Patch] support of cpu pools in xl"):
>>> On Fri, 2010-09-17 at 12:41 +0100, Juergen Gross wrote:
>>>> I just wanted to be able to support some (inactive) cpupools without any
>>>> cpu allocated. It's just a number which should normally be large enough.
>>>
>>> What is the purpose of these inactive cpupools?
>>
>> Amongst other things, I would guess, the creation or removal of
>> cpupools !

"Inactive cpupools" were meant to be cpupools without any cpus and domains
assigned to them.
They can exist for a short time during creation and removal, but due to
explicitly removing all cpus, too.

> I don't think so, libxl_create_cpupool returns a new poolid for a newly
> created pool, so they are not needed for that.

They have a poolid, but there might be more cpupools than cpus in the system.
This was the reason for the "+ 32". But I agree, this should be done via a
#define.

> BTW I noticed that we have libxl_list_pool vs
> libxl_{create,destroy}_cpupool and
> libxl_cpupool_{cpuadd,cpuremove,movedomain}. I think the interface
> should use cpupool throughout and not just pool to make it clear what it
> is a pool of. IOW libxl_list_pool should be libxl_list_cpupool, the type
> should be called  libxl_cpupool and functions such as
> libxl_name_to_poolid should instead be libxl_name_to_cpupoolid.

Okay, I'll change it.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2010-09-20  4:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17  6:10 [Patch] support of cpu pools in xl Juergen Gross
2010-09-17  9:46 ` Ian Campbell
2010-09-17 11:41   ` Juergen Gross
2010-09-17 11:55     ` Ian Campbell
2010-09-17 15:53       ` Ian Jackson
2010-09-17 18:28         ` Ian Campbell
2010-09-20  4:58           ` Juergen Gross [this message]
2010-09-29  8:28             ` Ian Campbell
2010-10-01  7:18               ` Juergen Gross
2010-10-01  7:47                 ` Ian Campbell
2010-09-17 15:55     ` Ian Jackson

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=4C96EA0E.7090105@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.