From: Sergio Belkin <sebelk@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Is still netperf a valid tool?
Date: Sun, 14 Jun 2020 11:36:56 -0300 [thread overview]
Message-ID: <CABZC=5zUvH0PZEoga2iWydJkVXOKMZCytQGuYV134aG3w9waPQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
Hi,
I've seen that many of the recommended tools to diagnose/troubleshoot
bufferbloat use netperf.
Netperf in https://github.com/HewlettPackard/netperf has many years of
inactivity. In fact, in recent versions of distros don't include it.
So, my question is: is still netperf a reliable tool?
Thanks in advance!
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
[-- Attachment #2: Type: text/html, Size: 715 bytes --]
next reply other threads:[~2020-06-14 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 14:36 Sergio Belkin [this message]
2020-06-14 14:55 ` Sebastian Moeller
2020-06-15 9:15 ` Toke Høiland-Jørgensen
2020-06-16 1:22 ` Sergio Belkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABZC=5zUvH0PZEoga2iWydJkVXOKMZCytQGuYV134aG3w9waPQ@mail.gmail.com' \
--to=sebelk@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox