From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt: Performance Regression 2.6.37 -> 2.6.38-rc8
Date: Wed, 9 Mar 2011 17:58:35 +0100 [thread overview]
Message-ID: <20110309165835.GA7855@fancy-poultry.org> (raw)
In-Reply-To: <20110308164508.GA8729@darkside.kls.lan>
On 09.03.2011, Mario 'BitKoenig' Holbe wrote:
> dm-crypt in 2.6.38 changed to per-CPU workqueues to increase it's
> performance by parallelizing encryption to multiple CPUs.
> This modification seems to cause (massive) performance drops for
> multiple parallel dm-crypt instances...
Not that it adresses your problem, but in my case, this patch is the
best one in the last months. On my good old primary LUKS/dmcrypt
encrypted partitions, on an AMD Quadcore, it boosts performance from
45 MB/s w/o the patch up to 87 MB/s with it. That's just an incredibly
huge performance boost.
next prev parent reply other threads:[~2011-03-09 16:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 16:45 [dm-crypt] dm-crypt: Performance Regression 2.6.37 -> 2.6.38-rc8 Mario 'BitKoenig' Holbe
2011-03-08 16:45 ` Mario 'BitKoenig' Holbe
2011-03-08 17:35 ` [dm-crypt] " Milan Broz
2011-03-08 19:23 ` Mario 'BitKoenig' Holbe
2011-03-08 19:23 ` Mario 'BitKoenig' Holbe
2011-03-08 20:07 ` Milan Broz
2011-03-08 20:17 ` Mario 'BitKoenig' Holbe
2011-03-08 20:17 ` Mario 'BitKoenig' Holbe
2011-03-09 16:58 ` Heinz Diehl [this message]
2011-03-10 16:57 ` Andi Kleen
2011-03-10 16:57 ` Andi Kleen
2011-03-10 17:54 ` [dm-crypt] " Mario 'BitKoenig' Holbe
2011-03-10 17:54 ` Mario 'BitKoenig' Holbe
2011-03-11 1:18 ` [dm-crypt] " Andi Kleen
2011-03-11 1:18 ` Andi Kleen
2011-03-11 18:03 ` [dm-crypt] " Mario 'BitKoenig' Holbe
2011-03-11 18:03 ` Mario 'BitKoenig' Holbe
2011-03-11 18:29 ` [dm-crypt] " Milan Broz
2011-03-11 18:29 ` Milan Broz
2011-03-11 18:36 ` [dm-crypt] " Andi Kleen
2011-03-11 18:36 ` Andi Kleen
2011-03-12 1:05 ` [dm-crypt] " Herbert Xu
2011-03-12 1:05 ` 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=20110309165835.GA7855@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.