From: Andi Kleen <ak@linux.intel.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Milan Broz <gmazyland@gmail.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: dm-crypt parallelization patches
Date: Tue, 3 Sep 2013 13:07:02 -0700 [thread overview]
Message-ID: <20130903200702.GJ16724@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1309031457480.28146@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, Sep 03, 2013 at 03:06:03PM -0400, 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.
The motivation for my patches was to make large systems with many
cores scale.
I think the motivation for yours is to make small systems without
hardware crypto offload slightly faster.
That's fine (although I suspect it's more and more obscure), as long as
you don't impact the large systems scalability.
Can you do some tests with a larger system with very parallel IO
(many CPUs submitting) and see if the IO rate is equivalent?
If that's given the patches are ok for me.
-Andi
next prev parent reply other threads:[~2013-09-03 20:07 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 [this message]
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
-- 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-crypt] [dm-devel] " Alasdair G Kergon
2013-03-26 20:05 ` Milan Broz
2013-03-26 20:28 ` [dm-crypt] " 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=20130903200702.GJ16724@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.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 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.