From: Evgeniy Polyakov <zbr@ioremap.net>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
linux-crypto@vger.kernel.org
Subject: Re: [RFC] [PATCH v2 0/4] Parallel IPsec
Date: Sat, 25 Apr 2009 12:38:49 +0400 [thread overview]
Message-ID: <20090425083849.GD26070@ioremap.net> (raw)
In-Reply-To: <20090424102451.GB12680@secunet.com>
Hi.
On Fri, Apr 24, 2009 at 12:24:51PM +0200, Steffen Klassert (steffen.klassert@secunet.com) wrote:
> This patchset adds the 'pcrypt' parallel crypto template. With this template it
> is possible to process the crypto requests of a transform in parallel without
> getting request reorder. This is in particular interesting for IPsec.
Why can't it be used by default for all crypto operations instead of
synchronous one?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2009-04-25 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 10:24 [RFC] [PATCH v2 0/4] Parallel IPsec Steffen Klassert
2009-04-24 10:26 ` [RFC] [PATCH v2 1/4] padata: generic interface for parallel processing Steffen Klassert
2009-04-27 8:56 ` Herbert Xu
2009-04-24 10:27 ` [RFC] [PATCH v2 2/4] pcrypt: Add pcrypt crypto parallelization engine Steffen Klassert
2009-04-27 8:56 ` Herbert Xu
2009-04-28 6:23 ` Steffen Klassert
2009-04-28 6:31 ` Herbert Xu
2009-04-28 6:41 ` Steffen Klassert
2009-04-24 10:28 ` [RFC] [PATCH v2 3/4] xfrm: Add a netlink attribute for software crypto accelerators Steffen Klassert
2009-04-27 8:53 ` Herbert Xu
2009-04-28 10:11 ` Steffen Klassert
2009-04-24 10:29 ` [RFC] [PATCH v2 4/4] esp: Use pcrypt if it is selected as software crypto accelerator Steffen Klassert
2009-04-25 8:38 ` Evgeniy Polyakov [this message]
2009-04-25 9:21 ` [RFC] [PATCH v2 0/4] Parallel IPsec Herbert Xu
2009-04-25 10:10 ` Evgeniy Polyakov
2009-04-25 10:56 ` 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=20090425083849.GD26070@ioremap.net \
--to=zbr@ioremap.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=steffen.klassert@secunet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).