From: tugouxp <13824125580@163.com>
To: musl@lists.openwall.com
Subject: [musl] Re:Re: [musl] Why the musl libc did not support neon simd acceleartor officially on mem* operations?
Date: Sat, 28 Aug 2021 22:29:18 +0800 (CST) [thread overview]
Message-ID: <6b183ce6.273f.17b8d2a34a5.Coremail.13824125580@163.com> (raw)
In-Reply-To: <20210828094847.GB3090@voyager>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
Thank you!
At 2021-08-28 17:48:47, "Markus Wichmann" <nullplan@gmx.net> wrote:
>On Sat, Aug 28, 2021 at 04:01:40PM +0800, tugouxp wrote:
>> HI guys:
>> I found that the current implmention of musl arm port memcpy.S and
>> other mem*.S operations did not use arm neon instructions, this
>> seems differenct with other counterparts like newlibc, glibc and
>> bonic libc, which all impl. the neon version of mem* operations.
>
>I am not an expert on this or indeed anything, but it seems like there
>are two plausible explanations for this:
>
>1.) Neon support is not architectural, and not subarchitectural. It
>appears Neon comes with a new register set the kernel has to switch out
>on context switch, so Neon support is predicated on kernel support. That
>makes it a runtime thing. Leaving aside where the kernel declares such
>support, having a runtime switch in memcpy() is going to be a slowdown
>of some kind for all existing users. I don't know how much of a
>slowdown, but a slowdown nonetheless.
>
>My guess is the other libcs ignore the issue of the user compiling a
>userspace that won't run on the target platform and allow the user to
>shoot themselves in the foot.
>
>Adverting to the competition is a poor choice for this mailing list, by
>the way, because part of musl's success comes from looking at them and
>saying: No, we are not going to do that.
>
>2.) The code does not exist because it has not been written yet. You are
>welcome to submit a patch. I mean, you found the mailing list easily
>enough.
>
>
>> so could you tell me why? is there and concern about on this in musl?
>> if i want to imple my self imple. how to do this, is there any matual
>> pathches to use?
>
>None that I am aware of, so they have not been submitted to this list
>for sure.
>
>Ciao,
>Markus
[-- Attachment #2: Type: text/html, Size: 2368 bytes --]
next prev parent reply other threads:[~2021-08-28 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 8:01 tugouxp
2021-08-28 9:48 ` Markus Wichmann
2021-08-28 14:29 ` tugouxp [this message]
2021-08-28 19:53 ` Rich Felker
2021-08-28 20:27 ` Jeffrey Walton
2021-08-28 20:34 ` Rich Felker
2021-09-04 13:56 ` Ismael Luceno
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=6b183ce6.273f.17b8d2a34a5.Coremail.13824125580@163.com \
--to=13824125580@163.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).