Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Dean Jenkins <djenkins@mvista.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: IPsec books and how to add async hardware encryption ?
Date: Mon, 3 Nov 2008 14:13:16 +0300	[thread overview]
Message-ID: <20081103111316.GA19920@ioremap.net> (raw)
In-Reply-To: <200811031050.59710.djenkins@mvista.com>

Hi Dean.

On Mon, Nov 03, 2008 at 10:50:59AM +0000, Dean Jenkins (djenkins@mvista.com) wrote:
> > cryptd is an software engine example of how hardware driver could be
> > implemented.
> 
> Are you saying that to implement an async hardware driver I could use the APIs 
> used by cryptd and create my own hwcryptd ?

Yes for the APIs used in cryptd, but usually hardware driver does not
need to have any threads attached, since completion of the event is
handled in the interrupt handler.

> If yes, is there any documentation for the APIs used by cryptd ?

No, there is no documentation except source code.
In some files you can even find this comments:

         * HEAVY TODO: needs to kick Herbert XU to write documentation.

Herbert is a crypto maintainer who created async crypto interfaces you
found in cryptd. You can also check hardware crypto drivers in
drivers/crypto/ directory.

-- 
	Evgeniy Polyakov

      reply	other threads:[~2008-11-03 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 15:08 IPsec books and how to add async hardware encryption ? Dean Jenkins
2008-10-31 20:32 ` Evgeniy Polyakov
2008-11-03 10:50   ` Dean Jenkins
2008-11-03 11:13     ` Evgeniy Polyakov [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=20081103111316.GA19920@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=djenkins@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox