kcryptd uses exorbient cpu during write
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
linux-ports-meta (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have my entire hard disk encrypted using dm-crypt (except a small boot partition). The encrypted partition is then used as a pv for LVM and then used for lvs.
alex@dell:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
alex@dell:~$ uname -a
Linux dell 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
alex@dell:~$ apt-cache policy linux-generic
linux-generic:
Installed: 2.6.28.11.15
Candidate: 2.6.28.11.15
Version table:
*** 2.6.28.11.15 0
500 http://
100 /var/lib/
When performing a write of any size larger than about 50MB, top indicates that kcryptd is taking up more cpu than anything else. With writes upwards in size of 250MB, my cpu gets saturated. In combination with rsync, this results in my computer being only barely usable until rsync finishes.
This did _not_ happen until I upgraded from Intrepid to Jaunty.
This is probably also relevant: I was running 32 bit Intrepid.