From: Christophe LEROY <christophe.leroy@c-s.fr>
To: Mathieu Malaterre <malat@debian.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Segher Boessenkool <segher@kernel.crashing.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] powerpc/lib: optimise PPC32 memcmp
Date: Wed, 30 May 2018 10:47:48 +0200 [thread overview]
Message-ID: <f2931bb1-2d56-8a5f-84b2-044f043b7633@c-s.fr> (raw)
In-Reply-To: <CA+7wUszdfG+u4YSnxjFaujy3s_Vu92POPamK+=zjYe6Pbu+kxw@mail.gmail.com>
Le 29/05/2018 à 22:03, Mathieu Malaterre a écrit :
> On Mon, May 28, 2018 at 12:49 PM, Christophe Leroy
> <christophe.leroy@c-s.fr> wrote:
>> At the time being, memcmp() compares two chunks of memory
>> byte per byte.
>>
>> This patch optimises the comparison by comparing word by word.
>>
>> A small benchmark performed on an 8xx comparing two chuncks
>> of 512 bytes performed 100000 times gives:
>>
>> Before : 5852274 TB ticks
>> After: 1488638 TB ticks
>>
>> This is almost 4 times faster
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>> ---
>> arch/powerpc/lib/string_32.S | 37 +++++++++++++++++++++++++++----------
>> 1 file changed, 27 insertions(+), 10 deletions(-)
>
> Would it possible for you to move the actual code instead to:
>
> ./arch/powerpc/lib/memcmp_32.S
>
> This will seat right next to memcmp_64.S implementation.
Good idea, thanks.
Done in v6
Christophe
>
>> diff --git a/arch/powerpc/lib/string_32.S b/arch/powerpc/lib/string_32.S
>> index 40a576d56ac7..4fbaa046aa84 100644
>> --- a/arch/powerpc/lib/string_32.S
>> +++ b/arch/powerpc/lib/string_32.S
>> @@ -16,17 +16,34 @@
>> .text
>>
>> _GLOBAL(memcmp)
>> - cmpwi cr0, r5, 0
>> - beq- 2f
>> - mtctr r5
>> - addi r6,r3,-1
>> - addi r4,r4,-1
>> -1: lbzu r3,1(r6)
>> - lbzu r0,1(r4)
>> - subf. r3,r0,r3
>> - bdnzt 2,1b
>> + srawi. r7, r5, 2 /* Divide len by 4 */
>> + mr r6, r3
>> + beq- 3f
>> + mtctr r7
>> + li r7, 0
>> +1: lwzx r3, r6, r7
>> + lwzx r0, r4, r7
>> + addi r7, r7, 4
>> + cmplw cr0, r3, r0
>> + bdnzt eq, 1b
>> + bne 5f
>> +3: andi. r3, r5, 3
>> + beqlr
>> + cmplwi cr1, r3, 2
>> + blt- cr1, 4f
>> + lhzx r3, r6, r7
>> + lhzx r0, r4, r7
>> + addi r7, r7, 2
>> + subf. r3, r0, r3
>> + beqlr cr1
>> + bnelr
>> +4: lbzx r3, r6, r7
>> + lbzx r0, r4, r7
>> + subf. r3, r0, r3
>> blr
>> -2: li r3,0
>> +5: li r3, 1
>> + bgtlr
>> + li r3, -1
>> blr
>> EXPORT_SYMBOL(memcmp)
>>
>> --
>> 2.13.3
>>
prev parent reply other threads:[~2018-05-30 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 10:49 [PATCH v5 0/3] powerpc/lib: Optimisation of memcmp() and __clear_user() for PPC32 Christophe Leroy
2018-05-28 10:49 ` [PATCH v5 1/3] powerpc/lib: move PPC32 specific functions out of string.S Christophe Leroy
2018-05-28 10:49 ` [PATCH v5 2/3] powerpc/lib: optimise 32 bits __clear_user() Christophe Leroy
2018-05-28 10:49 ` [PATCH v5 3/3] powerpc/lib: optimise PPC32 memcmp Christophe Leroy
2018-05-29 20:03 ` Mathieu Malaterre
2018-05-30 8:47 ` Christophe LEROY [this message]
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=f2931bb1-2d56-8a5f-84b2-044f043b7633@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=malat@debian.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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
all inboxes | Powered by JetHome®