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, 13 Nov 2014 17:25:29 -0800	[thread overview]
Message-ID: <54655A09.9000800@intel.com> (raw)
In-Reply-To: <20141114011911.GA10647@gondor.apana.org.au>

Hi Herbert,
On 11/13/2014 05:19 PM, Herbert Xu wrote:
>> > This way I can get much higher throughput than with algif_skcipher.
> Yes that's a worthy optimisation.  See if you can change the
> current implementation (without changing the interface) to achieve
> this.
Ok, I'll have a look. What about the asymmetric algorithms?
Regards,
Tadeusz

  reply	other threads:[~2014-11-14  1:28 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
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 [this message]
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=54655A09.9000800@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).