the CPU usage is zero, there is nothing popping up. The tasks causing the high load value are in D state. If I do "echo w > /proc/sysrq-trigger", I will get for every leaked NS:
I am not sure how fine is to have e.g. thousands of such leaked namespaces - if I can't run out of some resources (kworker threads?). I am going to keep the machine running + generate even higher load there to see if I hit any such limit.
Hi Dan,
the CPU usage is zero, there is nothing popping up. The tasks causing the high load value are in D state. If I do "echo w > /proc/sysrq- trigger" , I will get for every leaked NS:
[392149.562095] kworker/u81:40 D 0 4290 2 0x80000000 0x291/0x8a0 timeout+ 0x182/0x360 fn+0x130/ 0x130 run_todo+ 0x15e/0x5d0 0xe/0x10 device_ exit_batch+ 0x156/0x180 intr_irq+ 0x90/0x90 net+0x14e/ 0x2a0 one_work+ 0x1ec/0x410 thread+ 0x32/0x410 one_work+ 0x410/0x410 create_ on_node+ 0x70/0x70 64+0x67/ 0x130 group+0x14/ 0x20 fork+0x35/ 0x40
[392149.562112] Workqueue: netns cleanup_net
[392149.562125] Call Trace:
[392149.562135] __schedule+
[392149.562146] schedule+0x2c/0x80
[392149.562157] schedule_
[392149.562167] ? call_timer_
[392149.562177] msleep+0x2d/0x40
[392149.562188] ? msleep+0x2d/0x40
[392149.562199] netdev_
[392149.562210] rtnl_unlock+
[392149.562221] default_
[392149.562233] ? do_wait_
[392149.562245] cleanup_
[392149.562257] process_
[392149.562270] worker_
[392149.562281] kthread+0x128/0x140
[392149.562292] ? process_
[392149.562300] ? kthread_
[392149.562305] ? do_syscall_
[392149.562310] ? SyS_exit_
[392149.562316] ret_from_
I am not sure how fine is to have e.g. thousands of such leaked namespaces - if I can't run out of some resources (kworker threads?). I am going to keep the machine running + generate even higher load there to see if I hit any such limit.
Thanks
JH