From: Andi Kleen <andi@firstfloor.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-kernel@vger.kernel.org, mbroz@redhat.com,
Andi Kleen <andi@firstfloor.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH] DM-CRYPT: Scale to multiple CPUs
Date: Tue, 1 Jun 2010 09:21:15 +0200 [thread overview]
Message-ID: <20100601072115.GA30556@basil.fritz.box> (raw)
In-Reply-To: <4C040441.9020107@wpkg.org>
> Quite common to hit on a netbook/laptop with encrypted root these days,
> where storage can be relatively fast when compared to the speed of one of
> the cores of the (usually) multicore CPU.
My patch will help as long as the IO is submitted by multiple CPUs.
If that is not happening you would need pcrypt.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-06-01 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 18:47 [PATCH] DM-CRYPT: Scale to multiple CPUs Tomasz Chmielewski
2010-06-01 7:21 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 16:04 Andi Kleen
2010-05-31 16:34 ` Eric Dumazet
2010-05-31 17:46 ` Andi Kleen
2010-05-31 17:52 ` Eric Dumazet
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=20100601072115.GA30556@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=mbroz@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