linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Waiman Long <longman@redhat.com>
Subject: [PATCH] x86, locking: Inline *_unlock_bh & *_unlock_irqrestore
Date: Thu,  2 Feb 2017 13:36:29 -0500	[thread overview]
Message-ID: <1486060589-31572-1-git-send-email-longman@redhat.com> (raw)

For spinlock and read-write locks, both *_unlock() and *_unlock_irq()
functions are inlined if !PREEMPT. Whereas the *_unlock_bh() and
*unlock_irqrestore() are not inlined as that will increase the size
of the kernel binary.

Given the fact that the PV qspinlock unlock call is a callee-saved
function pointer, the unlock function is essentially a leaf function
if !PREEMPT is true under all circumstances. Inlining it will enable
the compiler to do much better optimization around the the unlock
call sites. Similarly for the read-write locks.

To unleash this additional performance, all these unlock functions
are now inlined for x86-64 kernel where kernel size is usually less
of a concern. For 32-bit kernel, it is assumed that the focus will
be a bit more on kernel size optimization and so those functions are
not inlined.

With 4.9.6 kernel source and gcc 4.8.5-11 compiler, the text size
of the base vmlinux binary increased from 8527918 bytes to 8462235
bytes. That was an increase of 0.78%.

On a 2-socket 24-core 48-thread system, the performance of the AIM7
high_systime workload (1000 users) increased from 209818.43 jobs/min
to 213333.33 jobs/min. That was an increase of 1.68%.

Signed-off-by: Waiman Long <longman@redhat.com>
---
 arch/x86/Kconfig | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 7b6fd68..a0fbed7 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -23,6 +23,12 @@ config X86_64
 	depends on 64BIT
 	# Options that are inherently 64-bit kernel only:
 	select ARCH_HAS_GIGANTIC_PAGE
+	select ARCH_INLINE_READ_UNLOCK_BH		if !PREEMPT
+	select ARCH_INLINE_READ_UNLOCK_IRQRESTORE	if !PREEMPT
+	select ARCH_INLINE_SPIN_UNLOCK_BH		if !PREEMPT
+	select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE	if !PREEMPT
+	select ARCH_INLINE_WRITE_UNLOCK_BH		if !PREEMPT
+	select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE	if !PREEMPT
 	select ARCH_SUPPORTS_INT128
 	select ARCH_USE_CMPXCHG_LOCKREF
 	select HAVE_ARCH_SOFT_DIRTY
-- 
1.8.3.1

             reply	other threads:[~2017-02-02 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 18:36 Waiman Long [this message]
2017-02-10 11:53 ` [PATCH] x86, locking: Inline *_unlock_bh & *_unlock_irqrestore Thomas Gleixner

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=1486060589-31572-1-git-send-email-longman@redhat.com \
    --to=longman@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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;
as well as URLs for NNTP newsgroup(s).