From: Ingo Molnar <mingo@kernel.org>
To: Wedson Almeida Filho <wedsonaf@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] x86: Use asm-goto to implement mutex fast path on x86-64
Date: Fri, 28 Jun 2013 13:19:48 +0200 [thread overview]
Message-ID: <20130628111948.GA31065@gmail.com> (raw)
In-Reply-To: <1372416851-56830-1-git-send-email-wedsonaf@gmail.com>
* Wedson Almeida Filho <wedsonaf@gmail.com> wrote:
> The new implementation allows the compiler to better optimize the code; the
> original implementation is still used when the kernel is compiled with older
> versions of gcc that don't support asm-goto.
>
> Compiling with gcc 4.7.3, the original mutex_lock() is 60 bytes with the fast
> path taking 16 instructions; the new mutex_lock() is 42 bytes, with the fast
> path taking 12 instructions.
>
> The original mutex_unlock() is 24 bytes with the fast path taking 7
> instructions; the new mutex_unlock() is 25 bytes (because the compiler used
> a 2-byte ret) with the fast path taking 4 instructions.
>
> The two versions of the functions are included below for reference.
>
> Old:
> ffffffff817742a0 <mutex_lock>:
> ffffffff817742a0: 55 push %rbp
> ffffffff817742a1: 48 89 e5 mov %rsp,%rbp
> ffffffff817742a4: 48 83 ec 10 sub $0x10,%rsp
> ffffffff817742a8: 48 89 5d f0 mov %rbx,-0x10(%rbp)
> ffffffff817742ac: 48 89 fb mov %rdi,%rbx
> ffffffff817742af: 4c 89 65 f8 mov %r12,-0x8(%rbp)
> ffffffff817742b3: e8 28 15 00 00 callq ffffffff817757e0 <_cond_resched>
> ffffffff817742b8: 48 89 df mov %rbx,%rdi
> ffffffff817742bb: f0 ff 0f lock decl (%rdi)
> ffffffff817742be: 79 05 jns ffffffff817742c5 <mutex_lock+0x25>
> ffffffff817742c0: e8 cb 04 00 00 callq ffffffff81774790 <__mutex_lock_slowpath>
> ffffffff817742c5: 65 48 8b 04 25 c0 b7 mov %gs:0xb7c0,%rax
> ffffffff817742cc: 00 00
> ffffffff817742ce: 4c 8b 65 f8 mov -0x8(%rbp),%r12
> ffffffff817742d2: 48 89 43 18 mov %rax,0x18(%rbx)
> ffffffff817742d6: 48 8b 5d f0 mov -0x10(%rbp),%rbx
> ffffffff817742da: c9 leaveq
> ffffffff817742db: c3 retq
>
> ffffffff81774250 <mutex_unlock>:
> ffffffff81774250: 55 push %rbp
> ffffffff81774251: 48 c7 47 18 00 00 00 movq $0x0,0x18(%rdi)
> ffffffff81774258: 00
> ffffffff81774259: 48 89 e5 mov %rsp,%rbp
> ffffffff8177425c: f0 ff 07 lock incl (%rdi)
> ffffffff8177425f: 7f 05 jg ffffffff81774266 <mutex_unlock+0x16>
> ffffffff81774261: e8 ea 04 00 00 callq ffffffff81774750 <__mutex_unlock_slowpath>
> ffffffff81774266: 5d pop %rbp
> ffffffff81774267: c3 retq
>
> New:
> ffffffff81774920 <mutex_lock>:
> ffffffff81774920: 55 push %rbp
> ffffffff81774921: 48 89 e5 mov %rsp,%rbp
> ffffffff81774924: 53 push %rbx
> ffffffff81774925: 48 89 fb mov %rdi,%rbx
> ffffffff81774928: e8 a3 0e 00 00 callq ffffffff817757d0 <_cond_resched>
> ffffffff8177492d: f0 ff 0b lock decl (%rbx)
> ffffffff81774930: 79 08 jns ffffffff8177493a <mutex_lock+0x1a>
> ffffffff81774932: 48 89 df mov %rbx,%rdi
> ffffffff81774935: e8 16 fe ff ff callq ffffffff81774750 <__mutex_lock_slowpath>
> ffffffff8177493a: 65 48 8b 04 25 c0 b7 mov %gs:0xb7c0,%rax
> ffffffff81774941: 00 00
> ffffffff81774943: 48 89 43 18 mov %rax,0x18(%rbx)
> ffffffff81774947: 5b pop %rbx
> ffffffff81774948: 5d pop %rbp
> ffffffff81774949: c3 retq
>
> ffffffff81774730 <mutex_unlock>:
> ffffffff81774730: 48 c7 47 18 00 00 00 movq $0x0,0x18(%rdi)
> ffffffff81774737: 00
> ffffffff81774738: f0 ff 07 lock incl (%rdi)
> ffffffff8177473b: 7f 0a jg ffffffff81774747 <mutex_unlock+0x17>
> ffffffff8177473d: 55 push %rbp
> ffffffff8177473e: 48 89 e5 mov %rsp,%rbp
> ffffffff81774741: e8 aa ff ff ff callq ffffffff817746f0 <__mutex_unlock_slowpath>
> ffffffff81774746: 5d pop %rbp
> ffffffff81774747: f3 c3 repz retq
Very nice!
One detail:
> +#if defined(CC_HAVE_ASM_GOTO)
> +#if defined(CC_HAVE_ASM_GOTO)
Please change these to #ifdef.
Thanks,
Ingo
next prev parent reply other threads:[~2013-06-28 11:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 10:54 [PATCH] x86: Use asm-goto to implement mutex fast path on x86-64 Wedson Almeida Filho
2013-06-28 11:19 ` Ingo Molnar [this message]
2013-06-28 14:09 ` Borislav Petkov
2013-06-28 14:12 ` H. Peter Anvin
2013-06-28 15:15 ` Peter Zijlstra
2013-06-28 16:41 ` [PATCH] x86, cpufeature: Use new CC_HAVE_ASM_GOTO Borislav Petkov
2013-07-05 14:24 ` [tip:x86/cpu] " tip-bot for Borislav Petkov
2013-06-29 23:56 ` [PATCH] x86: Use asm-goto to implement mutex fast path on x86-64 Wedson Almeida Filho
2013-06-30 22:00 ` Borislav Petkov
2013-07-01 7:50 ` Ingo Molnar
2013-07-01 10:23 ` Borislav Petkov
2013-07-01 11:11 ` Ingo Molnar
2013-07-01 12:29 ` Borislav Petkov
2013-07-01 12:50 ` Ingo Molnar
2013-07-01 14:48 ` Borislav Petkov
2013-07-01 22:28 ` Borislav Petkov
2013-07-01 22:35 ` Wedson Almeida Filho
2013-07-01 22:44 ` Borislav Petkov
2013-07-02 6:39 ` Ingo Molnar
2013-07-02 10:29 ` Borislav Petkov
2013-07-01 14:30 ` H. Peter Anvin
2013-07-01 14:36 ` Borislav Petkov
2013-07-01 14:45 ` H. Peter Anvin
2013-07-01 14:50 ` Borislav Petkov
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=20130628111948.GA31065@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wedsonaf@gmail.com \
--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.