From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Matthias-Christian Ott <ott@mirix.org>, linux-crypto@vger.kernel.org
Subject: Re: Hardware acceleration indication in af_alg
Date: Fri, 28 Oct 2011 18:24:46 +0200 [thread overview]
Message-ID: <4EAAD74E.7060202@gnutls.org> (raw)
In-Reply-To: <20111021132336.GA1080@gondor.apana.org.au>
On 10/21/2011 03:23 PM, Herbert Xu wrote:
> Matthias-Christian Ott <ott@mirix.org> wrote:
>> I did some experiments with af_alg and noticed that to be really
>> useful, it should indicate whether a certain algorithm is hardware
>> accelerated. I guess this has to be inferred by the priority of the
>> algorithm could be made available via a read-only socket option. Any
>> thoughts on this?
>>
>> I can imagine, an alternative approach and perhaps better approach
>> would be to measure the speed of the kernel provided algorithm against
>> a software implementation, but there are many other factors that could
>> influence the results. Therefore, it is perhaps better to just make
>> the assumption that hardware acceleration is faster which is made in
>> the kernel anyhow.
> You have to be careful to distinguish between hardware acceleration
> that is directly available to user-space (such as AESNI) and those
> that aren't.
How can this be done? The only driver field that could be used for that
is cra_priority and it seems it typically set to 300 irrespective of
instruction based crypto or external device.
regards,
Nikos
next prev parent reply other threads:[~2011-10-28 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 13:13 Hardware acceleration indication in af_alg Matthias-Christian Ott
2011-10-21 13:23 ` Herbert Xu
2011-10-21 14:15 ` Matthias-Christian Ott
2011-10-21 14:34 ` Matthias-Christian Ott
2011-10-28 16:24 ` Nikos Mavrogiannopoulos [this message]
2011-11-01 12:43 ` Nikos Mavrogiannopoulos
2011-11-01 12:59 ` Jamie Iles
2011-11-02 2:11 ` Nikos Mavrogiannopoulos
2011-11-02 22:51 ` Herbert Xu
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=4EAAD74E.7060202@gnutls.org \
--to=nmav@gnutls.org \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=ott@mirix.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;
as well as URLs for NNTP newsgroup(s).