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 RESEND 2/2] crypto: algif - change algif_skcipher to be asynchronous
Date: Mon, 09 Mar 2015 13:06:14 -0700	[thread overview]
Message-ID: <54FDFD36.5020204@intel.com> (raw)
In-Reply-To: <20150306120956.GA5715@gondor.apana.org.au>

On 03/06/2015 04:09 AM, Herbert Xu wrote:
>> It helps to make it faster.
>> > This way I can do some of the request setup beforehand and minimize overhead on the data path.
> Do you have numbers to back this up?

Ok, you are right. It was implemented that way when I used the qat type socket, which was rejected.
It made more sense to do it that way as there was some dma remapping that I could do upfront.
Now the difference in performance is negligible. I'll send v2 shortly.
Thanks for pointing this out.

  reply	other threads:[~2015-03-09 20:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 19:35 [PATCH RESEND 0/2] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-02-27 19:35 ` [PATCH RESEND 1/2] crypto: af_alg - Allow to link sgl Tadeusz Struk
2015-02-27 19:35 ` [PATCH RESEND 2/2] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-03-06 11:44   ` Herbert Xu
2015-03-06 12:04     ` Tadeusz Struk
2015-03-06 12:09       ` Herbert Xu
2015-03-09 20:06         ` Tadeusz Struk [this message]
2015-03-08 11:20 ` [PATCH RESEND 0/2] " Stephan Mueller
2015-03-09 15:10   ` Tadeusz Struk

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=54FDFD36.5020204@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).