mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Kconfig help entry for CONFIG_PARAVIRT_SPINLOCK
Date: Tue, 15 Oct 2013 23:45:58 +0200	[thread overview]
Message-ID: <932951750.20131015234558@eikelenboom.it> (raw)

Hi Raghavendra,

Since the ticketlock series have landed in this mergewindow (thanks :-) ) the
help accompanying the Kconfig entry doesn't seem to reflect the current state well.

- Wasn't the whole purpose of the ticketlock series to mitigate this 5% performance hit to something
  far less, so distro kernels could enable this for their normal kernels ?
  I don't have the exact performance figures though.

- Perhaps the suggestion to enable this for supported hypervisors (Xen and KVM ?) could be added ?

--
Sander


CONFIG_PARAVIRT_SPINLOCKS:

Paravirtualized spinlocks allow a pvops backend to replace the
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.

If you are unsure how to answer this question, answer N.

Symbol: PARAVIRT_SPINLOCKS [=y]
Type  : boolean
Prompt: Paravirtualization layer for spinlocks
  Location:
    -> Processor type and features
      -> Linux guest support (HYPERVISOR_GUEST [=y])
        -> Enable paravirtualization code (PARAVIRT [=y])
  Defined at arch/x86/Kconfig:632
  Depends on: HYPERVISOR_GUEST [=y] && PARAVIRT [=y] && SMP [=y]
  Selects: UNINLINE_SPIN_UNLOCK [=y]



             reply	other threads:[~2013-10-15 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 21:45 Sander Eikelenboom [this message]
2013-10-16  2:59 ` 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=932951750.20131015234558@eikelenboom.it \
    --to=linux@eikelenboom.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raghavendra.kt@linux.vnet.ibm.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

all inboxes | Powered by JetHome®