All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>,
	Andi Kleen <ak@linux.intel.com>,
	dm-crypt@saout.de, linux-kernel@vger.kernel.org,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: [dm-crypt] dm-crypt: Performance Regression 2.6.37 -> 2.6.38-rc8
Date: Fri, 11 Mar 2011 19:29:58 +0100	[thread overview]
Message-ID: <4D7A6A26.5000501@redhat.com> (raw)
In-Reply-To: <20110311180334.GA11382@darkside.kls.lan>

On 03/11/2011 07:03 PM, Mario 'BitKoenig' Holbe wrote:

>> You probably need to find some way
>> to make pcrypt (parallel crypt layer) work for dmcrypt. That may
>> actually give you more speedup too than your old hack because
>> it can balance over more cores. 

dmcrypt is already using async crypto interface, it is ready
for parallelization on this level.

Perhaps the problem is that pcrypt is not yet implemented for needed
algorithms?

Milan

WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <mbroz@redhat.com>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>,
	Andi Kleen <ak@linux.intel.com>,
	dm-crypt@saout.de, linux-kernel@vger.kernel.org,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: dm-crypt: Performance Regression 2.6.37 -> 2.6.38-rc8
Date: Fri, 11 Mar 2011 19:29:58 +0100	[thread overview]
Message-ID: <4D7A6A26.5000501@redhat.com> (raw)
In-Reply-To: <20110311180334.GA11382@darkside.kls.lan>

On 03/11/2011 07:03 PM, Mario 'BitKoenig' Holbe wrote:

>> You probably need to find some way
>> to make pcrypt (parallel crypt layer) work for dmcrypt. That may
>> actually give you more speedup too than your old hack because
>> it can balance over more cores. 

dmcrypt is already using async crypto interface, it is ready
for parallelization on this level.

Perhaps the problem is that pcrypt is not yet implemented for needed
algorithms?

Milan


  reply	other threads:[~2011-03-11 18:30 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
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         ` Milan Broz [this message]
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=4D7A6A26.5000501@redhat.com \
    --to=mbroz@redhat.com \
    --cc=Mario.Holbe@TU-Ilmenau.DE \
    --cc=agk@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=dm-crypt@saout.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.