DM-Devel Archive mirror
 help / color / mirror / Atom feed
From: dE <de.techno@gmail.com>
To: dm-devel@lists.linux.dev
Subject: Decrypting only uses 2 threads.
Date: Thu, 18 Apr 2024 21:45:01 +0530	[thread overview]
Message-ID: <CADofXPAz2v0teH91QtAzNQ5jfp8bU1+8hwoZUs-0h+G7KLdZkw@mail.gmail.com> (raw)

Hi.
    I'm trying to encrypt some block devices and trying to use a
cipher and mode which is multithreaded. I'm trying out
aes-ctr-essiv:sha256 to test multithreading, but have also tried
aes-xts-essiv:sha256 with the same result.

The encryption is definitely multithread (massively), but while
reading from the encrypted block device, I see that only 2 threads are
being used. As a result when the CPU is throttled (deliberately), I
see a drop in throughput while increased CPU utilization only in 2
cores.
The following commands were used to setup the encryption --

cryptsetup -y -d - -c aes-ctr-essiv:sha256 --key-size 256 create disk1 /dev/sda

Is there anything I can do to increase concurrency while decrypting?

                 reply	other threads:[~2024-04-18 16:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CADofXPAz2v0teH91QtAzNQ5jfp8bU1+8hwoZUs-0h+G7KLdZkw@mail.gmail.com \
    --to=de.techno@gmail.com \
    --cc=dm-devel@lists.linux.dev \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).