DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob-Tobias Winter <jakob-tobias.winter@1und1.de>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] dmcrypt performance / multithreading
Date: Mon, 28 Dec 2009 10:10:56 +0100	[thread overview]
Message-ID: <4B387620.8080606@1und1.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

hey there,

i'm currently at the chaos communications congress and am experiencing
difficulties with my crypto-performance.

there are two raidsets crypted with cryptsetup and therefore i get two
kcryptd processes. is there a way to get those processes to split into
per-cpu-prozesses?

the system is running Debian with 2.6.32.1 #2 SMP x86_64 GNU/Linux and
has 8 cpus, therefore enough power, if the process would offload work.

any advice or input you need to suggest a solution?

i did quite some googling and even found a kernel-commit which should du
just that, but can't seem to get it working.

you can also hit me via dect at the congress: 3445

-- wintix


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]

                 reply	other threads:[~2009-12-28  9:10 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=4B387620.8080606@1und1.de \
    --to=jakob-tobias.winter@1und1.de \
    --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