All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto/sha256.c crypto/sha512.c
Date: Tue, 27 Jan 2004 17:12:29 -0500	[thread overview]
Message-ID: <20040127221229.GA16413@certainkey.com> (raw)
In-Reply-To: <20040127130504.1c760026.davem@redhat.com>

I updated the faster_sha2.c to include a quick performance test, same URL.

The Ch/sec and Maj/sec can't be easily compared, however instruction
count can to some extent.

http://jlcooke.ca/lkml/faster_sha2_x86.s
http://jlcooke.ca/lkml/faster_sha2_ppc.s
http://jlcooke.ca/lkml/faster_sha2_alpha.s
http://jlcooke.ca/lkml/faster_sha2_sparc.s

Hope this helps, I'll know better next time I ask for patch-blessing.  :)

JLC


On Tue, Jan 27, 2004 at 01:05:04PM -0800, David S. Miller wrote:
> On Tue, 27 Jan 2004 15:22:25 -0500
> Jean-Luc Cooke <jlcooke@certainkey.com> wrote:
> 
> > The Ch() and Maj() operations are used a lot in sha256/512.
> 
> Your analysis is great, but James was really asking for numbers :-)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
http://www.certainkey.com
Suite 4560 CTTC
1125 Colonel By Dr.
Ottawa ON, K1S 5B6

  reply	other threads:[~2004-01-27 22:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 19:39 [PATCH] crypto/sha256.c crypto/sha512.c Jean-Luc Cooke
2004-01-27 20:14 ` James Morris
2004-01-27 20:22   ` Jean-Luc Cooke
2004-01-27 21:05     ` David S. Miller
2004-01-27 22:12       ` Jean-Luc Cooke [this message]
2004-01-28 21:30         ` Jean-Luc Cooke
2004-01-28 22:08           ` James Morris
2004-01-28 23:03             ` David S. Miller

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=20040127221229.GA16413@certainkey.com \
    --to=jlcooke@certainkey.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.