Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 2/3] crypto: algif_akcipher user space interface
Date: Thu, 23 Jul 2015 00:29:48 +0200	[thread overview]
Message-ID: <2141479.AxYfgguRCx@tachyon.chronox.de> (raw)
In-Reply-To: <55B01375.3040007@intel.com>

Am Mittwoch, 22. Juli 2015, 15:04:37 schrieb Tadeusz Struk:

Hi Tadeusz,

> On 07/22/2015 11:55 AM, Stephan Mueller wrote:
> > I concur with you. But we have only two options:
> > 
> > - either use SGLs which the current akcipher API does not do
> > 
> > - or do a memcpy of the sendpage data into the internal buffer
> 
> I would memcpy it here. Both the current software and QAT implementations
> do not support SGL so we'll end up memcpy it anyway.
> 
> > As the sendpage already has a speed penalty, I did not like the latter
> > one.
> > Based on my measurements for AEAD, Hash and skicpher, sendpage starts to
> > become faster than sendmsg with input buffers > 8 to 16 kBytes (sendpage
> > as at least 4 syscalls where sendmsg uses only two).
> > 
> > As our current akcipher API does not reach the mentioned limit, I opted to
> > require one sendpage call.
> > 
> > But if we change the akcipher API to SGLs, I will lift that limit.
> 
> As you said - the preferred way of invoking this would be sendmsg with data
> instead of splice. This is only to make splice happy in case the data is
> not in a contiguous buffer.

Good point.

I am waiting for Herbert for the decision on changing the akcipher to SGL. 
Based on that decision I either implement your suggestion (if we leave linear 
buffers) or I will go with preparing the SGL setup.

-- 
Ciao
Stephan

  reply	other threads:[~2015-07-22 22:30 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 [this message]
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
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=2141479.AxYfgguRCx@tachyon.chronox.de \
    --to=smueller@chronox.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=tadeusz.struk@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