From: Jeffrey Walton <noloader@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: SHA-accelerated Git
Date: Sun, 2 Jun 2019 06:43:07 -0400 [thread overview]
Message-ID: <CAH8yC8nMcVuLeLWrVumLaz2Pbi3GugzgY-Bw3SMipjJkaph85Q@mail.gmail.com> (raw)
Hi Everyone,
I have a lot of experience with cutting in SHA acceleration. I have no
experience with Git.
If someone would setup a fork and provide a call like:
// https://github.com/torvalds/linux/blob/master/arch/x86/include/asm/cpufeature.h
// Or whatever the project prefers
has_x86_sha = cpu_feature_enabled(X86_FEATURE_SHA_NI);
if (has_x86_sha)
{
sha1_hash_block(state, ptr, size);
}
And provide a stub:
sha1_hash_block(uint32_t* state, uint8_t* ptr, size_t size)
{
}
Then I would be happy to fill in the pieces.
I can also help with ARMv8.
In fact, if you want to use Andy Polyakov's asm from Cryptogams
(https://www.openssl.org/~appro/cryptogams/), then I can help with
that, too. Andy's skills are renowned and his code is used in the
kernel.
Jeff
next reply other threads:[~2019-06-02 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 10:43 Jeffrey Walton [this message]
2019-06-02 11:21 ` SHA-accelerated Git Michal Suchánek
2019-06-02 11:34 ` Jeffrey Walton
2019-06-03 10:14 ` Johannes Schindelin
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=CAH8yC8nMcVuLeLWrVumLaz2Pbi3GugzgY-Bw3SMipjJkaph85Q@mail.gmail.com \
--to=noloader@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).