Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1424248
| From | Stephan Mueller <smueller@chronox.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm |
| Date | 2016-06-16 18:30 +0200 |
| Message-ID | <rKIl3-2cb-25@gated-at.bofh.it> (permalink) |
| References | <rKfCp-Pv-9@gated-at.bofh.it> <rKHIm-1K6-29@gated-at.bofh.it> <rKI1I-25D-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am Donnerstag, 16. Juni 2016, 21:39:17 schrieb Raveendra Padasalagi: Hi Raveendra, > I need some clarification to address your comment > > "Shouldn't there be a priority here?" > > What I know regarding priority value for an algorithm > is higher the priority value it will be get selected for execution. > > For example, let's say for software implementation of the algorithm if > priority value > is specified as 100 and hardware driver implementation of the same > algorithm uses > the priority value of 300 then hardware algo is what selected for execution. > > I just had a look at priority value specified for other hash > algorithm's and none of the > software implementation specify any value, So it will be 0. > > I think it's okay to not to specify any priority value for software > implementation, > as hardware implementation can use non zero value if it needs higher > priority. > > What's your opinion ? You are fully correct. To be in line with the other hashes, maybe let us leave it at 0. I was thinking about "backend" ciphers that should never ever be selected (like the Intel AES-NI examples) which should have a lower prio than any other cipher. But then, they have unique cra_names, so it does not really matter :-) Ciao Stephan
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 1/2] Crypto: Add SHA-3 hash algorithm Raveendra Padasalagi <raveendra.padasalagi@broadcom.com> - 2016-06-15 11:50 +0200
Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Stephan Mueller <smueller@chronox.de> - 2016-06-15 13:50 +0200
Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Raveendra Padasalagi <raveendra.padasalagi@broadcom.com> - 2016-06-16 11:20 +0200
Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Stephan Mueller <smueller@chronox.de> - 2016-06-16 17:50 +0200
Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Raveendra Padasalagi <raveendra.padasalagi@broadcom.com> - 2016-06-16 18:10 +0200
Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Stephan Mueller <smueller@chronox.de> - 2016-06-16 18:30 +0200
csiph-web