Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: James Hartley <james.hartley@imgtec.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	galak@codeaurora.org, andrew.bresticker@chromium.org,
	ezequiel.garcia@imgtec.com, linux-crypto@vger.kernel.org
Subject: Re: [PATCH V3 1/2] crypto: Add Imagination Technologies hw hash accelerator
Date: Tue, 10 Mar 2015 20:37:07 +1100	[thread overview]
Message-ID: <20150310093707.GA17289@gondor.apana.org.au> (raw)
In-Reply-To: <1582962.nmzkjGWQFm@tauon>

On Mon, Mar 09, 2015 at 07:35:57AM +0100, Stephan Mueller wrote:
>
> >+static struct ahash_alg img_algs[] = {
> >+	{
> >+		.init = img_hash_init,
> >+		.update = img_hash_update,
> >+		.final = img_hash_final,
> >+		.finup = img_hash_finup,
> >+		.digest = img_hash_digest,
> >+		.halg = {
> >+			.digestsize = MD5_DIGEST_SIZE,
> >+			.base = {
> >+				.cra_name = "md5",
> >+				.cra_driver_name = "img-md5",
> >+				.cra_priority = 301,
> 
> Just curious: why do you use such odd priorities of 301 or 3000? IMHO, 
> all you need is a priority of more than 100 to "beat" the generic C 
> prios. Maybe you also need to beat the standard assembler 
> implementations which are routinely at 200 for hashes. So, a prio of 300 
> should suffice, should it not?

James, can you answer Stephan's question please?

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2015-03-10  9:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  2:58 [PATCH V3 0/2] Add support for the IMG hash accelerator James Hartley
2015-03-06  2:58 ` [PATCH V3 1/2] crypto: Add Imagination Technologies hw " James Hartley
2015-03-09  6:35   ` Stephan Mueller
2015-03-10  9:37     ` Herbert Xu [this message]
2015-03-10  9:53       ` James Hartley
2015-03-10  9:54       ` James Hartley
2015-03-10  9:55         ` Herbert Xu
2015-03-10 12:30           ` James Hartley
2015-03-06  2:58 ` [PATCH V3 2/2] Documentation: crypto: Add DT binding info for the img " James Hartley
     [not found] <1425610912-9930-1-git-send-email-james.hartley@imgtec.com>
     [not found] ` <1425610912-9930-2-git-send-email-james.hartley@imgtec.com>
2015-03-09  5:42   ` [PATCH V3 1/2] crypto: Add Imagination Technologies " Andrew Bresticker
2015-03-10 15:31     ` James Hartley
2015-03-10 18:02       ` Andrew Bresticker
2015-03-12  0:13         ` James Hartley

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=20150310093707.GA17289@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=andrew.bresticker@chromium.org \
    --cc=ezequiel.garcia@imgtec.com \
    --cc=galak@codeaurora.org \
    --cc=james.hartley@imgtec.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=smueller@chronox.de \
    /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