From: Milan Broz <mbroz@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: device-mapper development <dm-devel@redhat.com>,
herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
agk@redhat.com, ak@linux.intel.com
Subject: Re: [dm-devel] [PATCH] DM-CRYPT: Scale to multiple CPUs
Date: Mon, 31 May 2010 20:55:50 +0200 [thread overview]
Message-ID: <4C040636.8060702@redhat.com> (raw)
In-Reply-To: <20100531182724.GG10766@basil.fritz.box>
On 05/31/2010 08:27 PM, Andi Kleen wrote:
>>> AES-NI is not asynchronous and doesn't have limited resources.
>>
>> AES-NI used asynchronous crypto interface, was using asynchronous
>> crypto API cryptd daemon IIRC. So this changed?
>
> AFAIK all ciphers use the asynchronous interface, but that
> doesn't mean they are actually asynchronous. AES-NI certainly
> does not require running in a special thread. The only
> thing it doesn't support is running from interrupt context.
I mean how it is implemented now in crypto API, and I was almost
sure that aes-ni acceleration code uses cryptd (iow real asynchronous processing)
and also that not all CPU cores can run these instruction in parallel.
So I am mistaken here?
Milan
next prev parent reply other threads:[~2010-05-31 18:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 16:04 [PATCH] DM-CRYPT: Scale to multiple CPUs Andi Kleen
2010-05-31 16:34 ` Eric Dumazet
2010-05-31 17:46 ` Andi Kleen
2010-05-31 17:52 ` Eric Dumazet
2010-05-31 17:22 ` [dm-devel] " Milan Broz
2010-05-31 17:42 ` Andi Kleen
2010-05-31 18:10 ` Milan Broz
2010-05-31 18:27 ` Andi Kleen
2010-05-31 18:55 ` Milan Broz [this message]
2010-05-31 19:04 ` Andi Kleen
2010-05-31 22:07 ` Herbert Xu
2010-06-01 1:46 ` huang ying
2010-06-01 2:39 ` Mikulas Patocka
2010-06-01 2:44 ` Mikulas Patocka
2010-06-01 4:39 ` Herbert Xu
2010-06-02 5:10 ` Mikulas Patocka
2010-06-02 5:14 ` Herbert Xu
2010-06-02 5:25 ` Mikulas Patocka
2010-06-02 6:07 ` Herbert Xu
2010-06-02 6:30 ` Steffen Klassert
2010-06-02 7:07 ` Herbert Xu
2010-06-02 7:51 ` Andi Kleen
2010-06-01 6:40 ` Andi Kleen
2010-06-02 5:15 ` Mikulas Patocka
2010-06-02 5:20 ` Herbert Xu
2010-06-02 7:53 ` Andi Kleen
2010-06-02 10:20 ` 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=4C040636.8060702@redhat.com \
--to=mbroz@redhat.com \
--cc=agk@redhat.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@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