From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH] native inline gravatar
Date: Wed, 4 Jul 2018 01:49:13 +0200 [thread overview]
Message-ID: <CAHmME9qVOVi+J3_eh+DBsg0kk0HVknhu8RTU=HG6U=zt_p=fdQ@mail.gmail.com> (raw)
In-Reply-To: <153041523536.31775.12330787152148492370.stgit@mail.warmcat.com>
Sorry, but not a chance something like this can be accepted. This is
exactly the reason we put the time into making the Lua scripting
support. Is your reason for implementing this C performance? In that
case, could you send some performance metrics and some details about
your performance requirements on a given system? Considering the Lua
crypto module links against OpenSSL, I'm pretty sure that its hashing
performance will be considerably better the slow reference
implementation in this patch [1].
[1] https://github.com/openssl/openssl/blob/master/crypto/md5/asm/md5-x86_64.pl
next prev parent reply other threads:[~2018-07-03 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 3:20 andy
2018-07-03 23:49 ` Jason [this message]
2018-07-04 0:00 ` andy
2018-07-04 0:14 ` Jason
2018-07-04 0:28 ` andy
2018-07-04 0:34 ` Jason
2018-07-04 0:44 ` andy
2018-07-04 1:05 ` Jason
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='CAHmME9qVOVi+J3_eh+DBsg0kk0HVknhu8RTU=HG6U=zt_p=fdQ@mail.gmail.com' \
--to=cgit@lists.zx2c4.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.
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).