From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: make the dom0_max_vcpus option more flexible
Date: Fri, 4 May 2012 17:26:09 +0100 [thread overview]
Message-ID: <4FA40321.3080201@citrix.com> (raw)
In-Reply-To: <4FA41BF20200007800081BFE@nat28.tlf.novell.com>
On 04/05/12 17:12, Jan Beulich wrote:
>>>> On 04.05.12 at 18:01, David Vrabel <david.vrabel@citrix.com> wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> The dom0_max_vcpus command line option only allows the exact number of
>> VCPUs for dom0 to be set. It is not possible to say "up to N VCPUs
>> but no more than the number physically present."
>>
>> Add min: and max: prefixes to the option to set a minimum number of
>> VCPUs, and a maximum which does not exceed the number of PCPUs.
>>
>> For example, with "dom0_max_vcpus=min:4,max:8":
>
> Both "...max...=min:..." and "...max...=max:" look pretty odd to me;
> how about simply allowing a range along with a simple number (since
> negative values make no sense, omitting either side of the range would
> be supportable if necessary.
I was copying the way dom0_mem worked but yeah, it's not very pretty.
Is dom0_max_vcpus=<min>-<max> (e.g., dom0_max_vcpus=4-8) what you were
thinking of?
Using a single value would have to set both <min> and <max> or the
behaviour of the option changes (i.e., =N is the same as =N-N).
David
next prev parent reply other threads:[~2012-05-04 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 16:01 [PATCH] x86: make the dom0_max_vcpus option more flexible David Vrabel
2012-05-04 16:12 ` Jan Beulich
2012-05-04 16:26 ` David Vrabel [this message]
2012-05-04 18:18 ` David Vrabel
2012-05-07 8:19 ` Jan Beulich
2012-05-08 13:58 ` David Vrabel
2012-05-07 6:42 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2012-09-10 17:26 David Vrabel
2012-09-11 7:05 ` Jan Beulich
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=4FA40321.3080201@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).