From: Milan Broz <gmazyland@gmail.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Andi Kleen <ak@linux.intel.com>,
Milan Broz <gmazyland@gmail.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: dm-crypt parallelization patches
Date: Tue, 03 Sep 2013 22:49:08 +0200 [thread overview]
Message-ID: <52264B44.6050409@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1309031457480.28146@file01.intranet.prod.int.rdu2.redhat.com>
On 09/03/2013 09:06 PM, Mikulas Patocka wrote:
> Hi Andi
>
> You wrote the original dm-crypt paralllelization patch (commit
> c029772125594e31eb1a5ad9e0913724ed9891f2). This patch improves
> parallelization, it makes data being encrypted on the same CPU that
> submitted the request.
Hi Mikulas,
Do you have some recent reported performance problems with
the current dmcrypt code?
Please post numbers from tests. Also include systems using AES-NI.
You know I tested your patchset cca year ago and result was not clear
improvement... So if this changed, it is good news.
Milan
next prev parent reply other threads:[~2013-09-03 20:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 19:06 dm-crypt parallelization patches Mikulas Patocka
2013-09-03 20:07 ` Andi Kleen
2013-09-11 23:03 ` Mikulas Patocka
2013-09-11 23:33 ` Andi Kleen
2013-09-12 3:51 ` Milan Broz
2013-09-03 20:49 ` Milan Broz [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-26 3:47 dm-crypt performance Mikulas Patocka
2013-03-26 12:27 ` [dm-devel] " Alasdair G Kergon
2013-03-26 20:05 ` Milan Broz
2013-03-26 20:28 ` Mike Snitzer
2013-03-28 18:53 ` Tejun Heo
2013-03-28 19:33 ` Vivek Goyal
2013-03-28 19:44 ` Tejun Heo
2013-03-28 20:38 ` Vivek Goyal
2013-03-28 20:45 ` Tejun Heo
2013-04-09 17:51 ` dm-crypt parallelization patches Mikulas Patocka
2013-04-09 17:57 ` Tejun Heo
2013-04-09 18:08 ` Mikulas Patocka
2013-04-09 18:10 ` Tejun Heo
2013-04-09 18:42 ` Vivek Goyal
2013-04-09 18:57 ` Tejun Heo
2013-04-09 19:13 ` Vivek Goyal
2013-04-09 19:42 ` Mikulas Patocka
2013-04-09 19:52 ` Tejun Heo
2013-04-09 20:32 ` Mikulas Patocka
2013-04-09 21:02 ` Tejun Heo
2013-04-09 21:03 ` Tejun Heo
2013-04-09 21:07 ` Vivek Goyal
2013-04-09 21:18 ` Mikulas Patocka
2013-04-10 19:24 ` Vivek Goyal
2013-04-09 18:36 ` Vivek Goyal
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=52264B44.6050409@gmail.com \
--to=gmazyland@gmail.com \
--cc=agk@redhat.com \
--cc=ak@linux.intel.com \
--cc=dm-devel@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).