linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH RFC 4/4] crypto: qat - Add new algif interface for userspace
Date: Thu, 06 Nov 2014 19:43:23 -0800	[thread overview]
Message-ID: <545C3FDB.4010106@intel.com> (raw)
In-Reply-To: <20141107025607.GA9474@gondor.apana.org.au>

Hi Herbert,
On 11/06/2014 06:56 PM, Herbert Xu wrote:
>> Add new socket algif interface for userspace for symmetric and asymmetric
>> > crypto.
>> > 
>> > Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
> No this is not acceptable.  algif is meant to expose generic
> algorithms to user-space not a specific hardware implementation.

Yes, I know that PF_ALG wasn't designed to expose hardware specific
implementation, but the problem is that currently there is no interface
that allows using HW acceleration for algorithms such as RSA, DSA, or
Diffie-Hellman.
Using PF_ALG works perfectly for this purpose. I can get around 130K RSA
decrypt operations per second with 1024 bits modulus. This also scales
very well for more accelerators.
PF_ALG meant to be crypto interface for user space and this is what I'm
using it for here :) Is there any way I can make it (more) acceptable?
Regards,
Tadeusz

  reply	other threads:[~2014-11-07  3:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 19:59 [PATCH RFC 0/4] crypto: qat - Add userspace access to QAT services Tadeusz Struk
2014-11-06 19:59 ` [PATCH RFC 1/4] crytpo: qat - Fix 64 bytes requests Tadeusz Struk
2014-11-06 19:59 ` [PATCH RFC 2/4] crypto: qat - Add PKE firmware Tadeusz Struk
2014-11-06 19:59 ` [PATCH RFC 3/4] crypto: qat - Add userspace instances Tadeusz Struk
2014-11-06 19:59 ` [PATCH RFC 4/4] crypto: qat - Add new algif interface for userspace Tadeusz Struk
2014-11-07  2:56   ` Herbert Xu
2014-11-07  3:43     ` Tadeusz Struk [this message]
2014-11-07  4:05       ` Herbert Xu
2014-11-07  5:24         ` Tadeusz Struk
2014-11-07  5:31           ` Herbert Xu
2014-11-07 18:53             ` Tadeusz Struk
2014-11-07 19:48             ` Tadeusz Struk
2014-11-14  1:19               ` Herbert Xu
2014-11-14  1:25                 ` Tadeusz Struk
2014-11-14  1:29                   ` 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=545C3FDB.4010106@intel.com \
    --to=tadeusz.struk@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=qat-linux@intel.com \
    /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).