From: Andi Kleen <ak@linux.intel.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Herbert Xu <herbert@gondor.hengli.com.au>,
device-mapper development <dm-devel@redhat.com>,
linux-kernel@vger.kernel.org, agk@redhat.com
Subject: Re: [dm-devel] [PATCH] DM-CRYPT: Scale to multiple CPUs
Date: Wed, 02 Jun 2010 09:51:59 +0200 [thread overview]
Message-ID: <4C060D9F.3050600@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1006020119540.22695@hs20-bc2-1.build.redhat.com>
>>
>>> It is pointless to track the submitting CPU.
>>
>> No you are wrong.
>
> For what? For avoiding cache bounces? But the encrypting is
> order-of-magnitude slower than memory speed.
On a system with reasonably fast CPUs it's fastest to just stay
on your current CPU, don't try to talk to other CPUs, avoid
communication, just get the work done ASAP. But make
sure you can do this on multiple CPUs at the same time.
With AES-NI this becomes even more pronounced because it effectively
makes the CPU faster for encryption.
-andi
next prev parent reply other threads:[~2010-06-02 7:52 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
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 [this message]
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=4C060D9F.3050600@linux.intel.com \
--to=ak@linux.intel.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.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