linux-kernel - kworkers for dm-crypt locked to CPU core 0?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <51501C0A.5060406@digadd.de>
Date:	Mon, 25 Mar 2013 10:42:34 +0100
From:	Christian Schmidt <schmidt@...add.de>
To:	dm-crypt@...ut.de
CC:	linux-kernel@...r.kernel.org
Subject: kworkers for dm-crypt locked to CPU core 0?

Hi everyone,

I am trying to troubleshoot some strange performance issues I am seeing
on a machine of mine. Said machine had 10 drives mapped via separate
dm-crypt instances. The aggregate (read) throughput seems to hover
around 120-130MB/s (looking at iostat -x -d) when running an instance of
dd if=/dev/dm-<instance> of=/dev/null bs=1m for each mapping. However
"top" shows that one core is loaded with 99% system tasks, and two to
three cores are spinning in iowait. All the kworkers get their share of
roughly 10% CPU.

"taskset" shows that all of the kworkers have an affinity mask of 1, so
they can run on core 0 only, and trying to change it results in an error
of "Invalid argument".

Is there a way I can make the scheduler put those on multiple cores?

Please cc: me since I am not subscribed.

Regards,
Christian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/