mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lan Tianyu <tianyu.lan@intel.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, rkrcmar@redhat.com
Cc: pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM/x86: Increase max vcpu number to 352
Date: Fri, 11 Aug 2017 15:49:59 +0800	[thread overview]
Message-ID: <23159a7e-463a-2a5b-5aaa-ef7f0eb43547@intel.com> (raw)
In-Reply-To: <20170810175056.GR2547@char.us.oracle.com>

Hi Konrad:
	Thanks for your review.

On 2017年08月11日 01:50, Konrad Rzeszutek Wilk wrote:
> On Thu, Aug 10, 2017 at 06:00:59PM +0800, Lan Tianyu wrote:
>> Intel Xeon phi chip will support 352 logical threads. For HPC usage
>> case, it will create a huge VM with vcpu number as same as host cpus. This
>> patch is to increase max vcpu number to 352.
> 
> Why not 1024 or 4096?

This is on demand. We can set a higher number since KVM already has
x2apic and vIOMMU interrupt remapping support.

> 
> Are there any issues with increasing the value from 288 to 352 right now?

No found.

> 
> Also perhaps this should be made in an Kconfig entry?

That will be anther option but I find different platforms will define
different MAX_VCPU. If we introduce a generic Kconfig entry, different
platforms should have different range.

Radim & Paolo, Could you give some input? In qemu thread, we will set
max vcpu to 8192 for x86 VM. In KVM, The length of vcpu pointer array in
struct kvm and dest_vcpu_bitmap in kvm_irq_delivery_to_apic() are
specified by KVM_MAX_VCPUS. Should we keep align with Qemu?

-- 
Best regards
Tianyu Lan

  parent reply	other threads:[~2017-08-11  7:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 10:00 Lan Tianyu
     [not found] ` <20170810175056.GR2547@char.us.oracle.com>
2017-08-11  7:49   ` Lan Tianyu [this message]
2017-08-11  8:11     ` David Hildenbrand
2017-08-11 13:00       ` Radim Krčmář
2017-08-11 19:35         ` Konrad Rzeszutek Wilk
2017-08-15  3:00           ` Lan Tianyu
2017-08-15 14:10             ` Konrad Rzeszutek Wilk
2017-08-15 16:13               ` Radim Krčmář
2017-08-18 13:57                 ` Konrad Rzeszutek Wilk
2017-08-21 15:44                   ` Radim Krčmář
2017-08-16  3:07               ` Lan Tianyu
2017-08-18 14:20                 ` Konrad Rzeszutek Wilk
2017-08-15 14:20             ` Radim Krčmář
2017-08-11 22:47 ` Denys Vlasenko

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=23159a7e-463a-2a5b-5aaa-ef7f0eb43547@intel.com \
    --to=tianyu.lan@intel.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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

Powered by JetHome