From: Pedro Falcato <pedro.falcato@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] add memcmpeq: memcmp that returns length of first mismatch
Date: Thu, 29 Feb 2024 01:13:20 +0000 [thread overview]
Message-ID: <CAKbZUD3=7Mrfz9sCWO6EK0m9TwWvvDKtUAt73bJBSjoOsOZCwQ@mail.gmail.com> (raw)
In-Reply-To: <Zd_WjNcFLBWFkAIG@fuz.su>
On Thu, Feb 29, 2024 at 12:58 AM Robert Clausecker <fuz@fuz.su> wrote:
>
> Greetings,
>
> Am Thu, Feb 29, 2024 at 12:10:05AM +0000 schrieb Thorsten Glaser:
> > Pedro Falcato dixit:
> >
> > >Small note: This isn't quite true for remotely modern x86, unaligned
> >
> > It’s very much true, e.g. it breaks atomicity (ok, not relevant
> > *here*, but in general).
> >
> > AIUI, even modern amd64 chips of all vendors are reverting to
> > optimising rep movsb/lodsb instead again, for stringops.
>
> That is not the case. REP MOVSB and friends have a high startup latency,
> so you only want to use them for large-ish blocks. Too large and all of
> the sudden AVX-512 is faster again. For small blocks however, you do not
> want to use this instruction. It's indeed much better to do a pair of
> overlapping stores. They do not perform crazy well, but it's still better
> than all alternatives.
This. Plus the "FSRM" (fast short rep movsb) stuff is all fugazi - I'm
yet to see a microarchitecture where my GPR-only memcpy (which
resembles/resembled mjg@'s FreeBSD kernel memcpy, which you might've
read before) doesn't completely beat out rep movsb under ~256 bytes.
Oh n, and they're sometimes incredibly naive - the zen rep movsb's get
into an awful fallback mode (which I suspect is either byte-by-byte or
word-by-word) if you give it an unaligned buffer, it doesn't seem to
ever attempt to use wider stores.
Anyway, I digress, this is somewhat offtopic :)
--
Pedro
next prev parent reply other threads:[~2024-02-29 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 14:07 James Tirta Halim
2024-02-27 14:49 ` Rich Felker
2024-02-27 14:51 ` Rich Felker
2024-02-28 4:40 ` Markus Wichmann
2024-02-28 23:14 ` Thorsten Glaser
2024-02-29 0:02 ` Pedro Falcato
2024-02-29 0:10 ` Thorsten Glaser
2024-02-29 0:57 ` Robert Clausecker
2024-02-29 1:13 ` Pedro Falcato [this message]
2024-02-29 4:19 ` Markus Wichmann
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='CAKbZUD3=7Mrfz9sCWO6EK0m9TwWvvDKtUAt73bJBSjoOsOZCwQ@mail.gmail.com' \
--to=pedro.falcato@gmail.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).