All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] libxl: Make 'xl vcpu-set' work properly on overcommited hosts.
Date: Mon, 13 May 2013 07:00:07 +0200	[thread overview]
Message-ID: <51907357.3070900@ts.fujitsu.com> (raw)
In-Reply-To: <20130508223911.GA9226@phenom.dumpdata.com>

On 09.05.2013 00:39, Konrad Rzeszutek Wilk wrote:
>>>>> Well, overcommit comes in mind. Say you migrate to a 4PCPU box and you
>>>>> have 12VCPUs, then you decide to go down to 4, then back to 16 before
>>>>> migrating it to some other box. Can't do.
>>>>
>>>> You could do it *after* the migration back to a 16 way box n stead of
>>>> before though, which is most likely when you would actually want to do
>>>> it...
>>>
>>> I am kind of lost. Are we arguing for this being a bug or whether there is
>>> justification for putting in Xen 4.3?
>>
>> The former needs deciding before the latter.
>>
>> I'm not convinced that the current xl behaviour of refusing to
>> overcommit VCPUs on a host isn't the right one for the majority of use
>> cases. Obviously the silently refusing bit is a bug which should be
>> fixed.
>>
>> I don't buy that this is a "regression compared to Xend". It's certainly
>> a difference from how xend behaved but it seems on the whole to be a
>> positive one (i.e. xend was wrong).
>
> CC-ing Juergen here as he added this in.

I surely didn't mean to disable overcommitting. So I'm fine with your patch
to do the cpumap allocation with maxvcpus.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PBG PDG 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

  parent reply	other threads:[~2013-05-13  5:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 20:40 [PATCH] libxl: Make 'xl vcpu-set' work properly on overcommited hosts Konrad Rzeszutek Wilk
2013-05-08 10:32 ` George Dunlap
2013-05-08 10:46   ` Ian Campbell
2013-05-08 14:29     ` Konrad Rzeszutek Wilk
2013-05-08 15:04       ` Ian Campbell
2013-05-08 16:04         ` Ian Jackson
2013-05-08 16:35         ` Konrad Rzeszutek Wilk
2013-05-08 16:49           ` Ian Campbell
2013-05-08 17:05             ` Konrad Rzeszutek Wilk
2013-05-08 19:09               ` Ian Campbell
2013-05-08 22:39                 ` Konrad Rzeszutek Wilk
2013-05-09  8:43                   ` Ian Campbell
2013-05-09  9:09                   ` George Dunlap
2013-05-09 13:13                     ` Konrad Rzeszutek Wilk
2013-05-09 13:59                       ` George Dunlap
2013-05-10 18:05                         ` Ian Jackson
2013-05-13  5:00                   ` Juergen Gross [this message]
2013-05-08 16:03       ` Ian Jackson
2013-05-10 19:35         ` Konrad Rzeszutek Wilk
2013-05-13 14:02           ` Ian Jackson
2013-05-08 11:58   ` 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=51907357.3070900@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.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.