All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: dimitris@siganos.org, linux-crypto@vger.kernel.org,
	abadea@ixiacom.com, ddogaru@ixiacom.com
Subject: Re: ESP hardware acceleration
Date: Tue, 15 Sep 2009 12:12:52 -0500	[thread overview]
Message-ID: <20090915171252.GA30986@gondor.apana.org.au> (raw)
In-Reply-To: <200909151754.15716.opurdila@ixiacom.com>

Octavian Purdila <opurdila@ixiacom.com> wrote:
>
> AFAK, the crypto interface is asynchronous but the hashing interface (as used 
> in IPSec) is synchronous.
> 
> There are two patches I've recently seen on the list, one for converting to 
> async hashing and one for parallel crypto/ipsec which will probably get in 
> 2.6.32.

Yes they're now in Linus's tree so both hsahing and ciphers are
now async.

> However, I think that the best results for hw accel will be obtained if you 
> accelerate the AEAD interface.

If your driver benefits from seeing both the hashing request and the
cipher request at the same time then by all means go for the AEAD
interface.  But don't feel compelled to use it just because it's
there :)

> Speaking of hw accel, we are also playing with it and we got moderately good 
> results. We are now running into two major software bottlenecks: memcpy 
> (because of the copy required by TCP traffic) and CRC computation.

What platform is this? And where does CRC come into this?

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2009-09-15 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 13:19 ESP hardware acceleration Dimitrios Siganos
2009-09-15 14:54 ` Octavian Purdila
2009-09-15 17:12   ` Herbert Xu [this message]
2009-09-15 17:57     ` Octavian Purdila
2009-09-15 17:09 ` 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=20090915171252.GA30986@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=abadea@ixiacom.com \
    --cc=ddogaru@ixiacom.com \
    --cc=dimitris@siganos.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=opurdila@ixiacom.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.