* Kernel thread naming
@ 2019-06-26 14:40 Roman Mamedov
0 siblings, 0 replies; only message in thread
From: Roman Mamedov @ 2019-06-26 14:40 UTC (permalink / raw)
To: wireguard
Hello,
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,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-06-26 14:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-26 14:40 Kernel thread naming Roman Mamedov
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 NNTP newsgroup(s).