kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chegu Vinod <chegu_vinod@hp.com>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Avi Kivity <avi@redhat.com>,
	Gleb Natapov <gleb@redhat.com>, 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>,
	"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 RFC 0/2] kvm: Improving undercommit scenarios
Date: Wed, 28 Nov 2012 18:07:10 -0800	[thread overview]
Message-ID: <50B6C34E.20007@hp.com> (raw)
In-Reply-To: <20121126120740.2595.33651.sendpatchset@codeblue>

On 11/26/2012 4:07 AM, 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
> 4x   1784.3750   102.2699    2018.7500   187.5723    13.13485
> --+-----------+-----------+-----------+------------+-----------+
>
> --+-----------+-----------+-----------+------------+-----------+
>          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
> 4x  3043.1725  3243.7281    4664.4662   5946.5741      53.27643
> --+-----------+-----------+-----------+------------+-----------+
>
> 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 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(-)
>
> .
>
Tested-by: Chegu Vinod <chegu_vinod@hp.com>

  parent reply	other threads:[~2012-11-29  2:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 12:07 [PATCH V3 RFC 0/2] kvm: Improving undercommit scenarios Raghavendra K T
2012-11-26 12:07 ` [PATCH V3 RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task Raghavendra K T
2012-11-26 13:35   ` Andrew Jones
2012-11-27 10:30     ` Raghavendra K T
2012-11-27 14:04       ` Andrew Theurer
2012-11-28  7:03         ` Raghavendra K T
2012-11-27 14:23       ` Chegu Vinod
     [not found]         ` <50B68F94.3080907@hp.com>
2012-11-29  2:00           ` Andrew Theurer
     [not found]         ` <50B6B5B5.5060108@hp.com>
2012-11-29  2:20           ` Chegu Vinod
2012-12-14  0:29   ` Marcelo Tosatti
2012-12-14 15:40     ` Raghavendra K T
2012-12-19  5:35       ` Raghavendra K T
2012-11-26 12:08 ` [PATCH V3 RFC 2/2] kvm: Handle yield_to failure return code for potential undercommit case Raghavendra K T
2012-11-26 13:43   ` Andrew Jones
2012-11-26 14:06     ` Andrew Jones
2012-11-27 10:27     ` Raghavendra K T
2012-11-27 13:22       ` Andrew Jones
2012-11-28  1:12   ` Marcelo Tosatti
2012-11-28  5:10     ` Raghavendra K T
2012-11-29 12:16       ` Gleb Natapov
2012-11-30  5:04         ` Raghavendra K T
2012-12-03 19:56       ` Marcelo Tosatti
2012-12-04 17:49         ` Raghavendra K T
2012-12-06  6:59         ` Raghavendra K T
2012-12-08  0:49           ` Marcelo Tosatti
2012-11-29  2:07 ` Chegu Vinod [this message]
2012-11-29  9:49   ` [PATCH V3 RFC 0/2] kvm: Improving undercommit scenarios Raghavendra K T

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=50B6C34E.20007@hp.com \
    --to=chegu_vinod@hp.com \
    --cc=avi@redhat.com \
    --cc=drjones@redhat.com \
    --cc=gleb@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 \
    /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).