From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/3] AF_ALG interface for akcipher
Date: Tue, 21 Jul 2015 21:19:28 -0700 [thread overview]
Message-ID: <55AF19D0.5040700@intel.com> (raw)
In-Reply-To: <20150722013241.GA31240@gondor.apana.org.au>
On 07/21/2015 06:32 PM, Herbert Xu wrote:
> I think we should finish the conversion of the only in-kernel
> user of RSA before we add the user-space interface. Otherwise
> this unnecessarily ties our hands to the current API.
>
> For example, do we want an SG interface for the input and output?
> As it stands even if a hardware device came with SG support we
> would not be able to use it.
>
> Tadeusz, can you confirm again that qat does not support SG with
> respect to RSA input and output?
No, it doesn't. Even if we would add SG support on the API it will
need to be copied into contiguous buffers before it is sent to the HW.
Is there any other in-kernel user of RSA other than the module verifier?
If that's the only one I don't think we need any API changes.
I can refresh the old patches that converted it.
next prev parent reply other threads:[~2015-07-22 4:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 22:12 [PATCH 0/3] AF_ALG interface for akcipher Stephan Mueller
2015-07-21 22:12 ` [PATCH 1/3] crypto: af_alg - add sig gen / verify API Stephan Mueller
2015-07-21 22:13 ` [PATCH 2/3] crypto: algif_akcipher user space interface Stephan Mueller
2015-07-22 16:01 ` Tadeusz Struk
2015-07-22 18:55 ` Stephan Mueller
2015-07-22 22:04 ` Tadeusz Struk
2015-07-22 22:29 ` Stephan Mueller
2015-07-21 22:13 ` [PATCH 3/3] crypto: algif_akcipher - enable compilation Stephan Mueller
2015-07-22 1:32 ` [PATCH 0/3] AF_ALG interface for akcipher Herbert Xu
2015-07-22 4:19 ` Tadeusz Struk [this message]
2015-07-22 4:21 ` Herbert Xu
2015-07-22 11:58 ` Horia Geantă
2015-07-23 1:53 ` Herbert Xu
2015-07-23 5:14 ` Tadeusz Struk
2015-07-23 5:19 ` Herbert Xu
2015-07-23 10:16 ` Stephan Mueller
2015-07-22 7:14 ` Stephan Mueller
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=55AF19D0.5040700@intel.com \
--to=tadeusz.struk@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.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 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.