All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Iles <jamie.iles@picochip.com>
To: linux-crypto@vger.kernel.org
Subject: IPSec AH hardware offload
Date: Tue, 20 Jan 2009 14:14:48 +0000	[thread overview]
Message-ID: <20090120141448.GG3849@brook.picochip.com> (raw)

Hi,

I'm currently developing a driver for a hardware crypto offload engine that is
capable of offloading both ESP and AH in IPSec. I've noticed that none of the
crypto drivers in 2.6.28 do offload for ahash and that the netkey AH
implementation both use synchronous hashes. Are the synchronous software
versions likely to be more efficient than hardware offloading or is there an
architectural reason for not using async hashes?

Cheers,

    Jamie
This email and any files transmitted with it are confidential and intended solely for the use of the individuals to whom they are addressed. If you have received this email in error please notify the sender and delete the message from your system immediately.


             reply	other threads:[~2009-01-20 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 14:14 Jamie Iles [this message]
2009-01-28  3:37 ` IPSec AH hardware offload Herbert Xu
2009-01-28  8:36   ` Jamie Iles
2009-01-28 10:41     ` 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=20090120141448.GG3849@brook.picochip.com \
    --to=jamie.iles@picochip.com \
    --cc=linux-crypto@vger.kernel.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 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.