From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Optimize __arch_swab32 and __arch_swab16
Date: Sat, 10 Sep 2011 06:24:39 -0300 [thread overview]
Message-ID: <1315646679.455.38.camel@pasglop> (raw)
In-Reply-To: <1315570258-12275-1-git-send-email-Joakim.Tjernlund@transmode.se>
On Fri, 2011-09-09 at 14:10 +0200, Joakim Tjernlund wrote:
> PPC __arch_swab32 and __arch_swab16 generates non optimal code.
> They do not schedule very well, need to copy its input register
> and swab16 needs an extra insn to clear its upper bits.
> Fix this with better inline ASM.
>
> Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
> ---
> arch/powerpc/include/asm/swab.h | 28 ++++++++++++++--------------
> 1 files changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/swab.h b/arch/powerpc/include/asm/swab.h
> index c581e3e..3b9a200 100644
> --- a/arch/powerpc/include/asm/swab.h
> +++ b/arch/powerpc/include/asm/swab.h
> @@ -61,25 +61,25 @@ static inline void __arch_swab32s(__u32 *addr)
>
> static inline __attribute_const__ __u16 __arch_swab16(__u16 value)
> {
> - __u16 result;
> -
> - __asm__("rlwimi %0,%1,8,16,23"
> - : "=r" (result)
> - : "r" (value), "0" (value >> 8));
> - return result;
> + __asm__("rlwimi %0,%0,16,0x00ff0000\n\t"
> + "rlwinm %0,%0,24,0x0000ffff"
> + : "+r"(value));
> + return value;
> }
> #define __arch_swab16 __arch_swab16
I don't quite get the thing about needing to clear the high bits.
Value is a u16 to start with, %0 is pre-filled with value >> 8 which
won't add anything to the upper bits, neither will rlwimi, so why would
you need to clear upper bits ?
Now I do see why gcc might generate something sub-optimal here, but can
you provide examples of asm output before/after in the patch commit ?
> static inline __attribute_const__ __u32 __arch_swab32(__u32 value)
> {
> - __u32 result;
> -
> - __asm__("rlwimi %0,%1,24,16,23\n\t"
> - "rlwimi %0,%1,8,8,15\n\t"
> - "rlwimi %0,%1,24,0,7"
> - : "=r" (result)
> - : "r" (value), "0" (value >> 24));
> - return result;
> + __u32 tmp;
> +
> + __asm__("rlwimi %0,%1,24,0xffffffff"
> + : "=r" (value) : "r" (value));
> + tmp = value;
> + __asm__("rlwimi %0,%1,16,0x00ff0000"
> + : "+r" (value) : "r" (tmp));
> + __asm__("rlwimi %0,%1,16,0x000000ff"
> + : "+r" (value) : "r" (tmp));
> + return value;
> }
> #define __arch_swab32 __arch_swab32
Cheers,
Ben.
next prev parent reply other threads:[~2011-09-10 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 12:10 [PATCH] powerpc: Optimize __arch_swab32 and __arch_swab16 Joakim Tjernlund
2011-09-10 9:24 ` Benjamin Herrenschmidt [this message]
2011-09-11 9:32 ` Joakim Tjernlund
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=1315646679.455.38.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Joakim.Tjernlund@transmode.se \
--cc=linuxppc-dev@ozlabs.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 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).