From: Dario Faggioli <raistlin@linux.it>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH v3 ]libxl: allow to set more than 31 vcpus
Date: Fri, 01 Jun 2012 11:32:37 +0200 [thread overview]
Message-ID: <1338543157.31901.27.camel@Abyss> (raw)
In-Reply-To: <1338541118.17466.36.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2082 bytes --]
On Fri, 2012-06-01 at 09:58 +0100, Ian Campbell wrote:
> > > And, in future, there are some cases may not need to allocate max size cpumap too
> > > So it's better to extend the current interface.
> > >
> > Well, maybe... Who knows what future reserves ?!? :-D
> >
> > Anyway, although I see your point, I really really dislike the new
> > parameter in libxl_cpumap_alloc(),
>
> What about it do you dislike? The special meaning of 0 or its existence
> at all?
>
It's pretty much all about its existence, given the fact it is _always_
0 apart from one single case, where it could well be zero as well. :-)
It's just I find it uncomfortable to have it, but of course I could live
with it if it buys something. It's the latter I'm not sure I see...
> > but of course it is not something up
> > to me to decide, neither it is something I'd loose some sleep for. :-P
>
> You could give vcpus > pcpus (dumb, but e.g. for debugging) and in that
> case the existing libxl_cpumap_alloc behaviour (which sizes based on the
> # of phys cpus) is incorrect.
>
Mmm... Maybe this is still related to the fact that on all the test
boxes I've used, libxl_get_max_cpus() returns something higher than the
actual physical CPU count of those boxes themselves, but I just created
an 18 VCPUs VM on my 16 PCPUs test machine... I take the above like you
can't, can you?
Maybe it is that *_max_cpus() logic that needs some attention? :-O
> I suggested that rather than having
> libxl_cpumap_alloc_size() we just combine this with the existing fn with
> a new parameter.
>
Yeah, I checked that in the archives, and that's not the issue for me.
If the we decide we want the thing, I'm fine with both the 'add new' and
'modify the existing' approaches.
Thanks and Regards,
Dario
|
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-06-01 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 2:48 [PATCH v3 ]libxl: allow to set more than 31 vcpus Zhang, Yang Z
2012-06-01 6:35 ` Dario Faggioli
2012-06-01 7:18 ` Zhang, Yang Z
2012-06-01 8:44 ` Dario Faggioli
2012-06-01 8:58 ` Ian Campbell
2012-06-01 9:32 ` Dario Faggioli [this message]
2012-06-01 9:41 ` Ian Campbell
2012-06-01 10:23 ` Dario Faggioli
2012-06-01 10:38 ` Ian Campbell
2012-06-01 10:47 ` Dario Faggioli
2012-06-01 10:50 ` Ian Campbell
2012-06-01 11:04 ` Dario Faggioli
2012-06-01 11:09 ` Ian Campbell
2012-06-01 11:44 ` Ian Campbell
2012-06-22 12:11 ` Ian Campbell
2012-06-24 23:35 ` Zhang, Yang Z
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=1338543157.31901.27.camel@Abyss \
--to=raistlin@linux.it \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.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.