DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Merhaut <petermerhaut@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] slow read performance, but fast writes?
Date: Thu, 15 Sep 2011 13:07:46 +0200	[thread overview]
Message-ID: <4E71DC82.7050003@gmail.com> (raw)
In-Reply-To: <4E71D754.2050506@redhat.com>

Yeah but why is it using one cpu for encryption? I got 6 encrypted block
devices. When writing to them, all cpu cores are used for encryption,
therefor it's fast. When reading, it seems to use 1 cpu for all 6 crypto
threads?

Am 09/15/2011 12:45 PM, schrieb Milan Broz:
> On 09/15/2011 11:49 AM, Nikolay Kichukov wrote:
>> Hi,
>> this query is best suited for md-raid mailing list as what you measure:
>>
>> dd if=/dev/md3 of=/dev/null bs=1M
>>
>> does not involve any decryption. You are reading directly from the md device and there is no matter what is actually there.
> heh. I read that as crypt device and it is MD directly, sorry for confusion.
> Seems my brain is still in different timezone :)
>
> yes, this test has nothing to do with crypt.
>
> Anyway, it is interesting that the problem is there even without crypt,
> perhaps you should ask on linux-raid list then.
>
> for badblock - I guess it just submits all IO from one cpu,
> so only one core is used for encryption in fact. There applies the same what I wrote before.
>
> Milan

  reply	other threads:[~2011-09-15 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14 14:04 [dm-crypt] slow read performance, but fast writes? Peter Merhaut
2011-09-14 15:04 ` Arno Wagner
2011-09-14 16:47   ` Peter Merhaut
2011-09-15  9:49     ` Nikolay Kichukov
2011-09-15  9:53       ` Peter Merhaut
2011-09-15 10:45       ` Milan Broz
2011-09-15 11:07         ` Peter Merhaut [this message]
2011-09-14 15:15 ` Milan Broz

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=4E71DC82.7050003@gmail.com \
    --to=petermerhaut@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox