From: Ingo Molnar <mingo@elte.hu>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH v2 2/2] x86: Raise the hard VCPU count limit
Date: Thu, 21 Jul 2011 11:24:19 +0200 [thread overview]
Message-ID: <20110721092419.GQ9216@elte.hu> (raw)
In-Reply-To: <1310729869-1451-2-git-send-email-levinsasha928@gmail.com>
* Sasha Levin <levinsasha928@gmail.com> wrote:
> The patch raises the hard limit of VCPU count to 254.
>
> This will allow developers to easily work on scalability
> and will allow users to test high VCPU setups easily without
> patching the kernel.
>
> To prevent possible issues with current setups, KVM_CAP_NR_VCPUS
> now returns the recommended VCPU limit (which is still 64) - this
> should be a safe value for everybody, while a new KVM_CAP_MAX_VCPUS
> returns the hard limit which is now 254.
>
> Cc: Avi Kivity <avi@redhat.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: Pekka Enberg <penberg@kernel.org>
> Suggested-by: Pekka Enberg <penberg@cs.helsinki.fi>
> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
It would be nice to document the various internal limits that are
present (255, etc.) and which prevent further raising of
KVM_MAX_VCPUS.
This information got mapped out in this discussion, but the commit
loses it so it would be nice to preserve it somewhere (at least in
the changelog).
Thanks,
Ingo
next prev parent reply other threads:[~2011-07-21 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:37 [PATCH v2 1/2] KVM: MMIO: Lock coalesced device when checking for available entry Sasha Levin
2011-07-15 11:37 ` [PATCH v2 2/2] x86: Raise the hard VCPU count limit Sasha Levin
2011-07-21 9:24 ` Ingo Molnar [this message]
2011-07-18 8:11 ` [PATCH v2 1/2] KVM: MMIO: Lock coalesced device when checking for available entry Avi Kivity
2011-07-18 9:29 ` Sasha Levin
2011-07-18 9:50 ` Avi Kivity
2011-07-18 10:15 ` Sasha Levin
2011-07-18 11:43 ` Avi Kivity
2011-07-18 12:03 ` Sasha Levin
2011-07-18 12:29 ` Avi Kivity
2011-07-18 12:58 ` Sasha Levin
2011-07-18 13:11 ` Avi Kivity
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=20110721092419.GQ9216@elte.hu \
--to=mingo@elte.hu \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mtosatti@redhat.com \
--cc=penberg@kernel.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