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: Fri, 06 Mar 2015 12:04:49 +0000 [thread overview]
Message-ID: <54F997E1.8050601@intel.com> (raw)
In-Reply-To: <20150306114417.GA4949@gondor.apana.org.au>
On 03/06/2015 11:44 AM, Herbert Xu wrote:
> Are these separate caches really necessary? It looks like an
> overkill. What's wrong with just kmalloc?
Hi Herbert,
It helps to make it faster.
This way I can do some of the request setup beforehand and minimize overhead on the data path.
Thanks,
Tadeusz
next prev parent reply other threads:[~2015-03-06 12:08 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 [this message]
2015-03-06 12:09 ` Herbert Xu
2015-03-09 20:06 ` Tadeusz Struk
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=54F997E1.8050601@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 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.