All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] multiple crypt devices not using multiple CPUs
Date: Sun, 16 Dec 2012 22:25:07 +0100	[thread overview]
Message-ID: <50CE3C33.2040900@gmail.com> (raw)
In-Reply-To: <kald04$263$1@ger.gmane.org>

On 12/16/2012 10:04 PM, Brian J. Murrell wrote:
> Hi,
> 
> I guess I must be missing something.  I had understood that if one had
> multiple block devices being crypted by dm-crypt, if they were being
> operated on at the same time, their parallel crypto operations would
> utilize different CPUs.

In current kernels, work keeps on cpu which submitted it.

Please read
http://www.saout.de/pipermail/dm-crypt/2012-July/002582.html

(and try to run the second case with direct-io, iow add oflag=direct for dd)

m.

  reply	other threads:[~2012-12-16 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16 21:04 [dm-crypt] multiple crypt devices not using multiple CPUs Brian J. Murrell
2012-12-16 21:25 ` Milan Broz [this message]
2012-12-16 22:02   ` Brian J. Murrell

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=50CE3C33.2040900@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=brian@interlinx.bc.ca \
    --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.