diff options
| author | alfred <alfred@FreeBSD.org> | 2003-12-23 14:06:24 +0000 |
|---|---|---|
| committer | alfred <alfred@FreeBSD.org> | 2003-12-23 14:06:24 +0000 |
| commit | 52e8917de456385feec837884576ec44774e1a74 (patch) | |
| tree | 8611bf7bbe27f7d707bfea1c04ab382d8b0e3afe /usr.bin/netstat | |
| parent | a121c1dfef4ce13140b77ccd7844c4f0e8d1f829 (diff) | |
| download | FreeBSD-src-52e8917de456385feec837884576ec44774e1a74.zip FreeBSD-src-52e8917de456385feec837884576ec44774e1a74.tar.gz | |
I asked Bosko Milekic for help with 'peak' reporting, and he suggested
using the old 'cached' value but reporting it as 'cached'.
I've decided to report the 'cached' as 'peak', why? Well because
it is the peak, the peak of what is actually allocated. 'cached'
doesn't make sense to me as a user.
Diffstat (limited to 'usr.bin/netstat')
| -rw-r--r-- | usr.bin/netstat/mbuf.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/usr.bin/netstat/mbuf.c b/usr.bin/netstat/mbuf.c index 24d7c79..0e6e993 100644 --- a/usr.bin/netstat/mbuf.c +++ b/usr.bin/netstat/mbuf.c @@ -255,7 +255,7 @@ mbpr(u_long mbaddr, u_long mbtaddr __unused, u_long nmbcaddr, u_long nmbufaddr, } else { /* XXX: peak is now wrong. */ printf("%lu/%lu/%d (current/peak/max):\n", - totused[0], totused[0], nmbufs); + totused[0], totnum, nmbufs); } for (i = 0; cflag && i < (num_objs - 1); i++) { @@ -312,7 +312,7 @@ mbpr(u_long mbaddr, u_long mbtaddr __unused, u_long nmbcaddr, u_long nmbufaddr, } else { /* XXX: peak is now wrong. */ printf("%lu/%lu/%d (current/peak/max):\n", - totused[1], totused[1], nmbclusters); + totused[1], totnum, nmbclusters); } for (i = 0; cflag && i < (num_objs - 1); i++) { if (mbpstat[i]->mb_active == 0) |
