Re: 100% CPU time for sysctl command, not killable
- In reply to: Alexander Leidinger : "Re: 100% CPU time for sysctl command, not killable"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 30 Aug 2023 14:36:41 UTC
Am 2023-08-20 21:23, schrieb Alexander Leidinger: > Am 2023-08-20 18:55, schrieb Mina Galić: > procstat(1) kstack could be helpful here. > > -------- Original Message -------- > On 20 Aug 2023, 17:29, Alexander Leidinger Alexander@Leidinger.net> > wrote: > Hi, sysctl kern.maxvnodes=1048576000 results in 100% CPU and a > non-killable sysctl program. This is somewhat unexpected... Bye, > Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP > 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP > 0x8F31830F9F2772BF PID TID COMM TDNAME KSTACK 94391 118678 sysctl - sysctl_maxvnodes sysctl_root_handler_locked sysctl_root userland_sysctl sys___sysctl amd64_syscall fast_syscall_common I experimented a bit by multiplying my initial value of 104857600. It fails between 5 and 6 times the initial value. sysctl kern.maxvnodes=524288000 is successful within 4 seconds. sysctl kern.maxvnodes=629145600 goes into a loop with the same procstat -k output. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF