Date: Sat, 06 May 2023 20:13:25 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271246] Kernel wired memory leak with repeated netstat Message-ID: <bug-271246-227-KBc19tqmEL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271246-227@https.bugs.freebsd.org/bugzilla/> References: <bug-271246-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271246 --- Comment #8 from Dave Hayes <dave@jetcafe.org> --- First, I do understand that you want me to check for "the cause" and "the outstanding growing malloc zones".=20 Next I also do understand vmstat -z produces output related to zones, and vmstat -m produces output related to types.=20 You do not need to re-inform me of these ideas, but if you choose to again = that choice is out of my hands. I am not intending to frustrate you. :) My unanswered questions are based on the idea that the two switches to vmst= at produce hundreds of different data points: vmstat -z | wc -l 274 vmstat -z | wc -l 218 This is a lot of data (492 points) to check for changes. Naturally, I'd lik= e to reduce this check (which obviously has to be scripted) to data which is relevant.=20 With that, would you be so kind as to answer the following question? Are you asking me to check each and every entry for each switch -m and -z to vmstat to see what is growing OR is it possible to reduce the number of data points to a specific useful subset?=20 Thank you for your patience, as I am not a (modern) kernel dev. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271246-227-KBc19tqmEL>