Date: Fri, 24 Aug 2018 08:05:48 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230840] top - proposed enhancements Message-ID: <bug-230840-227-XMIVoZEBOO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230840-227@https.bugs.freebsd.org/bugzilla/> References: <bug-230840-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=3D230840 Michael Dexter <editor@callfortesting.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |editor@callfortesting.org --- Comment #3 from Michael Dexter <editor@callfortesting.org> --- Overheard: "top(1) began as a refreshing ps(1)" File system-related memory consumption by ARC, the L2ARC table, tmpfs(5), "malloc" md(4) devices are keen interest but we should be clear if top(1) is the place to put it. The first question is: Is the desired information available from the kernel= at this time or is it intertwined with other memory statistics? One thought: While gstat(8) is GEOM-specific, it would be nice if it would = be useful if it reported tmpfs(5) and md(4) activity. Following the top(1) mod= el, an optional header with longer-term statistics for ARC, tmpfs, md would be interesting: ARC: 12G Total, 3250M MFU, 8304M MRU, 1332K Anon, 134M Header, 439M Other 7572M Compressed, 33G Uncompressed, 4.53:1 Ratio L2ARC: Table 2G (other stats?) tmpfs: 34G (other stats?) md: 2G (other stats?) dT: 1.008s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 0 0 0 0.0 0 0 0.0 0.0| da0 0 0 0 0 0.0 0 0 0.0 0.0| da1 0 0 0 0 0.0 0 0 0.0 0.0| da2 0 0 0 0 0.0 0 0 0.0 0.0| da3 0 0 0 0 0.0 0 0 0.0 0.0| cd0 0 0 0 0 0.0 0 0 0.0 0.0| md0 0 0 0 0 0.0 0 0 0.0 0.0| tmpfsfoo --=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-230840-227-XMIVoZEBOO>