Cool, the rrul_be_irtt test is working for me. I see what you mean, ideally it
would just be the same test but you substitute the tool you want to use for a
particular measurement.
Maybe this is what you're saying, but could it be that you specify what tool
you want to use for each particular measurement? In other words, the tool for
'TCP throughput' is netperf as of now, and later could possibly be iperf. For
'UDP RTT' it can be netperf or irtt. For 'ICMP RTT' it can be ping or fping,
etc.
I'm waving my arms here because there can be more than one measurement from a
single tool. So maybe it should really be 'UDP RT' because in the case of irtt
it's doing a UDP round-trip and measuring several things from it at once: RTT,
OWD, IPDV, etc. Since there isn't a one-to-one correspondence between the tool
and measurement it returns, it's not clear to me yet how it should be
specified, still thinking about it.
I guess at some point there will be additional plots for OWD and IPDV. Is it a
new situation for you that the plots available depend not only on the test but
the tool used or even its settings?
Personally I don't think it's necessary to check for server-side support. If
someone is specifying they want to use a particular tool, I think they're
declaring that it's available, as it is today with netperf / netserver.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/106#issuecomment-344883874
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
