All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org, gleb@redhat.com,
	pbonzini@redhat.com, tglx@linutronix.de, linux@eikelenboom.it,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] x86 kconfig: Add recommendation to enable paravirt spinlock
Date: Mon, 21 Oct 2013 12:30:38 -0400	[thread overview]
Message-ID: <20131021163038.GA17709@phenom.dumpdata.com> (raw)
In-Reply-To: <1382371508-3843-1-git-send-email-raghavendra.kt@linux.vnet.ibm.com>

On Mon, Oct 21, 2013 at 09:35:08PM +0530, Raghavendra K T wrote:
> Since paravirt spinlock optimization are in 3.12 kernel, we have
> very good performance benefit for paravirtualized KVM / Xen kernel.
> Also we no longer suffer from 5% side effect on native kernel.

Yeey!
> 
> Signed-off-by: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
> ---
>  Would like to thank Sander for spotting and suggesting this.
>  pvspinlock benefit on KVM link: https://lkml.org/lkml/2013/8/6/178 
>  
>  Attilio's tests on native kernel impact:
>  http://blog.xen.org/index.php/2012/05/11/benchmarking-the-new-pv-ticketlock-implementation/
> 
>  arch/x86/Kconfig | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index f67e839..4ba9d32 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -638,10 +638,10 @@ config PARAVIRT_SPINLOCKS
>  	  spinlock implementation with something virtualization-friendly
>  	  (for example, block the virtual CPU rather than spinning).
>  
> -	  Unfortunately the downside is an up to 5% performance hit on
> -	  native kernels, with various workloads.
> +	  It has minimal impact on native kernels and gives nice performance
> +	  benefit for paravirtualized KVM / Xen kernels.
>  
> -	  If you are unsure how to answer this question, answer N.
> +	  If you are unsure how to answer this question, answer Y.
>  
>  source "arch/x86/xen/Kconfig"
>  
> -- 
> 1.7.11.7
> 

  reply	other threads:[~2013-10-21 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 16:05 [PATCH] x86 kconfig: Add recommendation to enable paravirt spinlock Raghavendra K T
2013-10-21 16:30 ` Konrad Rzeszutek Wilk [this message]
2013-10-26 13:50 ` [tip:core/locking] x86/locking/kconfig: Update paravirt spinlock Kconfig description tip-bot for 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=20131021163038.GA17709@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=raghavendra.kt@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.