Date: Tue, 3 Dec 2024 18:00:25 +0800 From: Zhenlei Huang <zlei@FreeBSD.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: "src-committers@freebsd.org" <src-committers@FreeBSD.org>, "dev-commits-src-all@freebsd.org" <dev-commits-src-all@FreeBSD.org>, "dev-commits-src-main@freebsd.org" <dev-commits-src-main@FreeBSD.org> Subject: Re: git: b5a8abe9502e - main - How to show interface traffic in bits per second Message-ID: <AF8F6D23-05F8-4D78-871A-CDA99C2D1C85@FreeBSD.org> In-Reply-To: <202412030755.4B37tO1k018962@critter.freebsd.dk> References: <202412022113.4B2LD0mt010926@gitrepo.freebsd.org> <043A2EA2-647F-4B04-B6AA-A3E6B001B741@FreeBSD.org> <EDA68984-3DB1-4872-A319-67E68B8F810A@FreeBSD.org> <202412030755.4B37tO1k018962@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Dec 3, 2024, at 3:55 PM, Poul-Henning Kamp <phk@phk.freebsd.dk> = wrote: >=20 > -------- > Zhenlei Huang writes: >=20 >> When netstat reports every 8 seconds, you're gonna get `8 * bytes per = 8=20 >> seconds`, so you still get `bytes per second` but not `bits per = second`=20 >=20 > Netstat -I reports bytes since last update, not bytes per second. Yeah, you're right. I think I over thought this and got confused by `per = second` :-) >=20 > --=20 > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe =20 > Never attribute to malice what can adequately be explained by = incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AF8F6D23-05F8-4D78-871A-CDA99C2D1C85>