From: Denys Vlasenko <vda.linux@googlemail.com>
To: musl <musl@lists.openwall.com>
Subject: Re: [PATCH 1/2] x86_64/memset: avoid multiply insn if possible
Date: Thu, 12 Feb 2015 20:26:27 +0100 [thread overview]
Message-ID: <CAK1hOcPVMiQo=fdRJSSMH6vx22aDbTcxjf_tFVphhNE8Szi6RQ@mail.gmail.com> (raw)
In-Reply-To: <20150212172735.GX23507@brightrain.aerifal.cx>
On Thu, Feb 12, 2015 at 6:27 PM, Rich Felker <dalias@libc.org> wrote:
> On Thu, Feb 12, 2015 at 06:17:02PM +0100, Denys Vlasenko wrote:
>> memset is very, very often called with fill=0,
>> and 64-bit imul is expensive on many CPUs.
>> Avoid it if fill=0.
>>
>> Also avoid multiply on "short memset" codepath if possible,
>> and when we do need it, use 32-bit one, which is cheaper on many CPUs.
>
> I'd actually like to extend the "short" range up to at least 32 bytes
> using two 8-byte writes for the middle, unless the savings from using
> 32-bit imul instead of 64-bit are sufficient to justify 4 4-byte
> writes for the middle. On the cpu I tested on, the difference is 11
> cycles vs 32 cycles for non-rep path versus rep path at size 32.
The short path causes mixed feelings in me.
On one hand, it's elegant in a contrived way.
On the other hand, multiple
overlaying stores must be causing hell in store unit.
I'm thinking, maybe there's a faster way to do that.
Can you post your memset testsuite?
next prev parent reply other threads:[~2015-02-12 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 17:17 Denys Vlasenko
2015-02-12 17:17 ` [PATCH 2/2] x86_64/memset: align destination to 8 byte boundary Denys Vlasenko
2015-02-12 17:27 ` [PATCH 1/2] x86_64/memset: avoid multiply insn if possible Rich Felker
2015-02-12 19:26 ` Denys Vlasenko [this message]
2015-02-12 20:36 ` Denys Vlasenko
2015-02-13 7:24 ` Rich Felker
2015-02-13 16:38 ` 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='CAK1hOcPVMiQo=fdRJSSMH6vx22aDbTcxjf_tFVphhNE8Szi6RQ@mail.gmail.com' \
--to=vda.linux@googlemail.com \
--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).