Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Koen Kooi <koen.kooi@linaro.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] openssl: switch ARM builds from linux-elf-arm to linux-armv4 config
Date: Wed, 16 Oct 2013 10:20:25 +0100	[thread overview]
Message-ID: <1381915225.3917.45.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1381908355-18124-1-git-send-email-koen@dominion.thruhere.net>

On Wed, 2013-10-16 at 09:25 +0200, Koen Kooi wrote:
> From: Koen Kooi <koen.kooi@linaro.org>
> 
> This enables aes and sha1 assembly at buildtime. Openssl does a
> runtime check to see which portion gets enabled.

[...]

> Algo    blocksize       ops/s after
>                 ops/s before    difference
> -------------------------------------------
> MD5	16	308,766	264,664	-14.28%
> 	64	277,090	263,340	-4.96%
> 	256	212,652	197,043	-7.34%
> 	1024	103,604	100,157	-3.33%
> 	8192	17,936	17,796	-0.78%

Do you know why it's causing MD5 to get slower?  I guess md5 with
blocksize=16 is not a very common case, but still.

Also, it seems generally a bit unwholesome for openssl to be picking its
own CFLAGS at all.  Would it be better to just make it use the same
CFLAGS as everything else?

p.




  reply	other threads:[~2013-10-16  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  7:25 [PATCHv2] openssl: switch ARM builds from linux-elf-arm to linux-armv4 config Koen Kooi
2013-10-16  9:20 ` Phil Blundell [this message]
2013-10-16  9:45   ` Koen Kooi
2013-10-17  5:54     ` Koen Kooi

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=1381915225.3917.45.camel@x121e.pbcl.net \
    --to=pb@pbcl.net \
    --cc=koen.kooi@linaro.org \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.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