From: Pavel Roskin <proski@gnu.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: roberto.sassu@polito.it, linux-crypto@vger.kernel.org
Subject: Re: Converting mac80211 CCMP to packet-at-a-time processing
Date: Tue, 16 Mar 2010 02:21:14 -0400 [thread overview]
Message-ID: <1268720474.26820.36.camel@mj> (raw)
In-Reply-To: <20100313122847.GA26337@gondor.apana.org.au>
On Sat, 2010-03-13 at 20:28 +0800, Herbert Xu wrote:
> Pavel Roskin <proski@gnu.org> wrote:
> >
> > However, it's disappointing that the caller needs to deal explicitly
> > with completions. The blkcipher API is much simpler. I would have hard
> > time advocating a patch to CCMP that makes the code more complicated.
>
> You won't have to deal with completions if you allocate your
> algorithm with the CRYPTO_ALG_ASYNC bit off. Of course you won't
> be able to use most hardware accelerations either.
Actually, I thought using CRYPTO_ALG_ASYNC in the mask meant to
_exclude_ asynchronous algorithms.
Is there any documentation for Linux crypto API that documents use of
CRYPTO_ALG_ASYNC? Also, I'd like to know meanings of
CRYPTO_TFM_REQ_MAY_BACKLOG and CRYPTO_TFM_REQ_MAY_SLEEP.
The crypto API feels like a minefield to me - I should check everything
in the code or even experiment to figure out how the public API works.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-16 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:49 Converting mac80211 CCMP to packet-at-a-time processing Roberto Sassu
2010-03-13 3:42 ` Pavel Roskin
2010-03-13 12:28 ` Herbert Xu
2010-03-16 6:21 ` Pavel Roskin [this message]
2010-03-18 8:19 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2010-03-12 5:29 Pavel Roskin
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=1268720474.26820.36.camel@mj \
--to=proski@gnu.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=roberto.sassu@polito.it \
/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.