From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>, linux-crypto@vger.kernel.org
Subject: Re: [RFC] [PATCH v2 2/4] pcrypt: Add pcrypt crypto parallelization engine
Date: Tue, 28 Apr 2009 08:41:57 +0200 [thread overview]
Message-ID: <20090428064157.GB20366@secunet.com> (raw)
In-Reply-To: <20090428063129.GA1776@gondor.apana.org.au>
On Tue, Apr 28, 2009 at 02:31:29PM +0800, Herbert Xu wrote:
>
> I thought so. The system is certainly not going to automatically
> construct a second pcrypt algorithm once one exists. So I think
> we can just remove this bit.
>
Ok, so I will remove it in the next version.
Steffen
next prev parent reply other threads:[~2009-04-28 6:39 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 [this message]
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 ` [RFC] [PATCH v2 0/4] Parallel IPsec Evgeniy Polyakov
2009-04-25 9:21 ` 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=20090428064157.GB20366@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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;
as well as URLs for NNTP newsgroup(s).