From: Gleb Natapov <gleb@redhat.com>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Avi Kivity <avi.kivity@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Rik van Riel <riel@redhat.com>,
Srikar <srikar@linux.vnet.ibm.com>,
"Nikunj A. Dadhania" <nikunj@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>, Jiannan Ouyang <ouyang@cs.pitt.edu>,
Chegu Vinod <chegu_vinod@hp.com>,
"Andrew M. Theurer" <habanero@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Srivatsa Vaddagiri <srivatsa.vaddagiri@gmail.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH V3 RESEND RFC 0/2] kvm: Improving undercommit scenarios
Date: Tue, 29 Jan 2013 16:05:58 +0200 [thread overview]
Message-ID: <20130129140558.GF15004@redhat.com> (raw)
In-Reply-To: <20130122073854.24731.9426.sendpatchset@codeblue.in.ibm.com>
On Tue, Jan 22, 2013 at 01:08:54PM +0530, Raghavendra K T wrote:
> In some special scenarios like #vcpu <= #pcpu, PLE handler may
> prove very costly, because there is no need to iterate over vcpus
> and do unsuccessful yield_to burning CPU.
>
> The first patch optimizes all the yield_to by bailing out when there
> is no need to continue in yield_to (i.e., when there is only one task
> in source and target rq).
>
> Second patch uses that in PLE handler. Further when a yield_to fails
> we do not immediately go out of PLE handler instead we try thrice
> to have better statistical possibility of false return. Otherwise that
> would affect moderate overcommit cases.
>
> Result on 3.7.0-rc6 kernel shows around 140% improvement for ebizzy 1x and
> around 51% for dbench 1x with 32 core PLE machine with 32 vcpu guest.
>
>
> base = 3.7.0-rc6
> machine: 32 core mx3850 x5 PLE mc
>
> --+-----------+-----------+-----------+------------+-----------+
> ebizzy (rec/sec higher is beter)
> --+-----------+-----------+-----------+------------+-----------+
> base stdev patched stdev %improve
> --+-----------+-----------+-----------+------------+-----------+
> 1x 2511.3000 21.5409 6051.8000 170.2592 140.98276
> 2x 2679.4000 332.4482 2692.3000 251.4005 0.48145
> 3x 2253.5000 266.4243 2192.1667 178.9753 -2.72169
> --+-----------+-----------+-----------+------------+-----------+
>
> --+-----------+-----------+-----------+------------+-----------+
> dbench (throughput in MB/sec. higher is better)
> --+-----------+-----------+-----------+------------+-----------+
> base stdev patched stdev %improve
> --+-----------+-----------+-----------+------------+-----------+
> 1x 6677.4080 638.5048 10098.0060 3449.7026 51.22643
> 2x 2012.6760 64.7642 2019.0440 62.6702 0.31639
> 3x 1302.0783 40.8336 1292.7517 27.0515 -0.71629
> --+-----------+-----------+-----------+------------+-----------+
>
> Here is the refernce of no ple result.
> ebizzy-1x_nople 7592.6000 rec/sec
> dbench_1x_nople 7853.6960 MB/sec
>
> The result says we can still improve by 60% for ebizzy, but overall we are
> getting impressive performance with the patches.
>
> Changes Since V2:
> - Dropped global measures usage patch (Peter Zilstra)
> - Do not bail out on first failure (Avi Kivity)
> - Try thrice for the failure of yield_to to get statistically more correct
> behaviour.
>
> Changes since V1:
> - Discard the idea of exporting nrrunning and optimize in core scheduler (Peter)
> - Use yield() instead of schedule in overcommit scenarios (Rik)
> - Use loadavg knowledge to detect undercommit/overcommit
>
> Peter Zijlstra (1):
> Bail out of yield_to when source and target runqueue has one task
>
> Raghavendra K T (1):
> Handle yield_to failure return for potential undercommit case
>
> Please let me know your comments and suggestions.
>
> Link for the discussion of V3 original:
> https://lkml.org/lkml/2012/11/26/166
>
> Link for V2:
> https://lkml.org/lkml/2012/10/29/287
>
> Link for V1:
> https://lkml.org/lkml/2012/9/21/168
>
> kernel/sched/core.c | 25 +++++++++++++++++++------
> virt/kvm/kvm_main.c | 26 ++++++++++++++++----------
> 2 files changed, 35 insertions(+), 16 deletions(-)
Applied, thanks.
--
Gleb.
prev parent reply other threads:[~2013-01-29 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:38 [PATCH V3 RESEND RFC 0/2] kvm: Improving undercommit scenarios Raghavendra K T
2013-01-22 7:39 ` [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task Raghavendra K T
2013-01-24 10:32 ` Ingo Molnar
2013-01-25 10:40 ` Raghavendra K T
2013-01-25 10:47 ` Ingo Molnar
2013-01-25 15:54 ` Raghavendra K T
2013-01-25 18:49 ` Ingo Molnar
2013-01-27 16:58 ` Raghavendra K T
2013-01-25 11:05 ` Andrew Jones
2013-01-25 15:58 ` Raghavendra K T
2013-01-22 7:39 ` [PATCH V3 RESEND RFC 2/2] kvm: Handle yield_to failure return code for potential undercommit case Raghavendra K T
2013-01-23 13:57 ` [PATCH V3 RESEND RFC 0/2] kvm: Improving undercommit scenarios Andrew Jones
2013-01-24 8:27 ` Raghavendra K T
2013-01-29 14:05 ` Gleb Natapov [this message]
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=20130129140558.GF15004@redhat.com \
--to=gleb@redhat.com \
--cc=avi.kivity@gmail.com \
--cc=chegu_vinod@hp.com \
--cc=drjones@redhat.com \
--cc=habanero@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=ouyang@cs.pitt.edu \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=srivatsa.vaddagiri@gmail.com \
--cc=tglx@linutronix.de \
/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