mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] x86_64/memset: use "small block" code for blocks up to 30 bytes long
Date: Sat, 14 Feb 2015 23:06:55 -0500	[thread overview]
Message-ID: <20150215040655.GM23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150214193533.GK23507@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]

On Sat, Feb 14, 2015 at 02:35:33PM -0500, Rich Felker wrote:
> On Fri, Feb 13, 2015 at 05:39:49PM +0100, Denys Vlasenko wrote:
> > Before this change, we were using it only for 15-byte blocks and smaller.
> > Measurements on Sandy Bridge CPU show that "rep stosq" setup time
> > is high enough to dominate speed of fills well above that size:
> 
> I just ran some tests with the latest three patches, including this
> one, and aside from the significant improvement for sizes 16-30 in
> this last patch, each patch makes various sizes 2-15 mildly slower. A
> few of them go from 9 cycles to 11 cycles average; most just increase
> by 1 cycle. And all sizes 8 and under are still slower than the C
> code.
> 
> I don't think these small sizes are a typical deliberate usage case
> for memset, but even just a couple cycles is a large relative
> difference at such sizes, and they could arise in generic code (think
> something like qsort which uses memcpy possibly with small sizes, but
> something using memset instead) and make a significant performance
> difference.
> 
> The main change whose value I really question is the conditional
> widen_rax. If the value isn't used until a few cycles after the imul
> instruction, doing it unconditionally is probably cheaper than testing
> and branching even when the branch is predictable.

To elaborate, simply replacing the unconditional imul with an
unconditional xor %eax,%eax in my best variant so far, I was only able
to save one cycle. So I don't see any way a test, branch, and
conditional imul could be less expensive than the unconditional imul.

I'm attaching my current draft based on the ideas so far in this
thread. See how it compares to your version(s) in the timing tests
you're using/on your hardware.

Rich

[-- Attachment #2: my2.s --]
[-- Type: text/plain, Size: 1070 bytes --]

.global memset
.type memset,@function
memset:
	movzbq %sil,%rax
	mov $0x101010101010101,%r8
	imul %r8,%rax

	lea -1(%rdx),%rcx
	cmp $126,%rcx
	jae 2f

	mov %sil,(%rdi)
	mov %sil,-1(%rdi,%rdx)
	cmp $2,%edx
	jbe 1f

	mov %ax,1(%rdi)
	mov %ax,(-1-2)(%rdi,%rdx)
	cmp $6,%edx
	jbe 1f

	mov %eax,(1+2)(%rdi)
	mov %eax,(-1-2-4)(%rdi,%rdx)
	cmp $14,%edx
	jbe 1f

	mov %rax,(1+2+4)(%rdi)
	mov %rax,(-1-2-4-8)(%rdi,%rdx)
	cmp $30,%edx
	jbe 1f

	mov %rax,(1+2+4+8)(%rdi)
	mov %rax,(1+2+4+8+8)(%rdi)
	mov %rax,(-1-2-4-8-16)(%rdi,%rdx)
	mov %rax,(-1-2-4-8-8)(%rdi,%rdx)
	cmp $62,%edx
	jbe 1f

	mov %rax,(1+2+4+8+16)(%rdi)
	mov %rax,(1+2+4+8+16+8)(%rdi)
	mov %rax,(1+2+4+8+16+16)(%rdi)
	mov %rax,(1+2+4+8+16+24)(%rdi)
	mov %rax,(-1-2-4-8-16-32)(%rdi,%rdx)
	mov %rax,(-1-2-4-8-16-24)(%rdi,%rdx)
	mov %rax,(-1-2-4-8-16-16)(%rdi,%rdx)
	mov %rax,(-1-2-4-8-16-8)(%rdi,%rdx)
	
1:	mov %rdi,%rax
	ret

2:	test %rdx,%rdx
	jz 1b

	mov %rdi,%r8
	mov %rax,(%rdi)
	mov %rax,-16(%rdi,%rdx)
	mov %rax,-8(%rdi,%rdx)
	add $8,%rdi
	sub $8,%rcx
	and $-8,%rdi
	shr $3,%rcx
	rep
	stosq
	mov %r8,%rax
	ret

  reply	other threads:[~2015-02-15  4:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 16:39 Denys Vlasenko
2015-02-14 19:35 ` Rich Felker
2015-02-15  4:06   ` Rich Felker [this message]
2015-02-15 14:07     ` Denys Vlasenko
2015-02-15 15:03       ` Rich Felker
2015-02-15 21:44         ` Denys Vlasenko
2015-02-15 22:55           ` Rich Felker
2015-02-16 10:09             ` Denys Vlasenko
2015-02-16 15:12               ` Rich Felker
2015-02-16 17:36           ` Rich Felker
2015-02-17 13:08             ` Denys Vlasenko
2015-02-17 16:12               ` Rich Felker
2015-02-17 16:51                 ` Denys Vlasenko
2015-02-17 17:30                   ` Denys Vlasenko
2015-02-17 17:40                   ` Rich Felker
2015-02-17 18:53                     ` Denys Vlasenko
2015-02-17 21:12                       ` Rich Felker
2015-02-18  9:05                         ` Denys Vlasenko

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=20150215040655.GM23507@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).