From: Stephan Mueller <smueller@chronox.de>
To: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: communicating from the user space
Date: Mon, 23 Feb 2015 09:17 +0100 [thread overview]
Message-ID: <4767408.E4yQUuQjlM@tachyon.chronox.de> (raw)
In-Reply-To: <1424640392.22199.3.camel@gnutls.org>
Am Sonntag, 22. Februar 2015, 22:26:32 schrieb Nikos Mavrogiannopoulos:
Hi Nikos,
> On Sun, 2015-02-22 at 16:04 +0100, Stephan Mueller wrote:
> > Am Sonntag, 22. Februar 2015, 18:32:34 schrieb sri sowj:
> >
> > Hi sri,
> >
> > > Hi Stephen,
> > >
> > > It was a great information with respective PF_ALG , I have explored a
> > > bit on openssl and algorithms prospect , Please let me know if
> > > anything to add to it.
> > >
> > > openssl crypto engine:
> > >
> > > below are the steps to enable openssl to communicate using pf/af_alg.
> > >
> > > #1:git clone http://src.carnivore.it/users/common/af_alg/
> >
> > Yes, that is it. But it is not fully efficient as it does not use vmsplice
> > where appropriate. So, libkcapi should be faster in several use cases.
>
> When would vmsplice be appropriate? As far as I understand vmsplice adds
> a cost on operations for small data, which is the majority of use cases
> in crypto. In the measurements I did for cryptodev-linux [0] vmsplice
> did improve performance only for more than 64k packets which is never
> the case with real world crypto (TLS has a maximum of 14k for example).
According to my measurements, I have the following heuristic for symmetric
ciphers: if the ciphertext is less than 1<<13, then use one sendmsg call.
Otherwise use vmsplice.
For AEAD, my library uses 3 IOVecs which means that sendmsg is faster in any
case (the overhead for setting up 3 IOVecs in kernel space for vmsplice is
higher than sendmsg copy).
For hashes, I yet have to make the measurements.
>
> regards,
> Nikos
>
> [0]. http://cryptodev-linux.org/comparison.html
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ciao
Stephan
prev parent reply other threads:[~2015-02-23 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 19:57 communicating from the user space sri sowj
2015-02-20 20:58 ` Stephan Mueller
2015-02-21 3:09 ` sri sowj
2015-02-21 7:01 ` Stephan Mueller
2015-02-22 13:02 ` sri sowj
2015-02-22 15:04 ` Stephan Mueller
2015-02-22 15:41 ` sri sowj
2015-02-22 19:15 ` Stephan Mueller
2015-02-22 21:26 ` Nikos Mavrogiannopoulos
2015-02-23 4:06 ` sri sowj
2015-02-23 8:18 ` Stephan Mueller
2015-02-23 8:30 ` Nikos Mavrogiannopoulos
2015-02-23 8:27 ` Nikos Mavrogiannopoulos
2015-02-23 15:47 ` sri sowj
2015-02-23 8:17 ` Stephan Mueller [this message]
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=4767408.E4yQUuQjlM@tachyon.chronox.de \
--to=smueller@chronox.de \
--cc=linux-crypto@vger.kernel.org \
--cc=nmav@gnutls.org \
/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