Kernel thread naming

Roman Mamedov rm at
Wed Jun 26 16:40:46 CEST 2019


Today I noticed there are kernel threads named "wg-crypt-wgX" (the latter part
being name of the interface). However when there is actual load on WG, these
don't seem to be active, and in "top" we still see a bunch of "kworker/0:X"
using the CPU.

Would it be possible to give those kworkers recognizable names instead?
I remember Btrfs had a change like this in the past, first they had all
kworkers, and now a whole assortment of threads like "btrfs-cleaner",
"btrfs-transacti" or "btrfs-endio-met" (there's some strict length limit).

With respect,

More information about the WireGuard mailing list