Date: Sun, 5 Nov 2000 14:12:41 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Mike Smith <msmith@FreeBSD.ORG>, Poul-Henning Kamp <phk@critter.freebsd.dk>, hackers@FreeBSD.ORG Subject: Re: user-space resource information... Message-ID: <20001105141241.A19227@panzer.kdm.org> In-Reply-To: <3A051B10.3E43D0C9@newsguy.com>; from dcs@newsguy.com on Sun, Nov 05, 2000 at 05:32:16PM %2B0900 References: <3248.973365649@critter> <200011041952.eA4JqZF11774@mass.osd.bsdi.com> <20001104221812.A14843@panzer.kdm.org> <3A051B10.3E43D0C9@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 05, 2000 at 17:32:16 +0900, Daniel C. Sobral wrote: > "Kenneth D. Merry" wrote: > > > > I think vmstat(8) might be a better fit than iostat. vmstat already > > displays kernel memory usage (-m), interrupt usage (-i), paging stats (-s), > > and zone allocator stats (-z). > > That's vmstat's problem, not a feature. :-) > > That kind of thinking is what led to Linux /proc. > > > Since vmstat already has "kitchen sink" type functionality (i.e. a wide > > variety of uses), I think it would probably work better to put this new > > functionality there. > > If it's not vm-related, it shouldn't be listed by vmstat. Interrupts aren't vm-related either, yet vmstat displays them. > > iostat is also designed primarily for continuous output use -- displaying a > > line of stats every N seconds. vmstat is also designed for that in its > > That's the objection I raised to Mike. :-) I suggested systat, though > that has it's problems too. Well, perhaps this stuff should go in its own utility, since it doesn't really seem to fit anywhere else. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001105141241.A19227>