Closed GoogleCodeExporter closed 8 years ago
This label should show up as a field in the JSON output as well.
Original comment by jdu...@es.net
on 6 Jun 2013 at 12:45
Original comment by bltier...@es.net
on 23 Jul 2013 at 5:47
Here is an example from nuttcp that demonstrates this:
nuttcp -T20 -i1 -w400M -xc 2/2 -Is1 -p 5500 10.26.0.132 & nuttcp -T20 -i1
-w400M -xc 3/3 -Is2 -p 5501 10.26.0.132
s1: 45.3750 MB / 1.00 sec = 380.6160 Mbps 0 retrans
s2: 40.1250 MB / 1.00 sec = 336.5865 Mbps 0 retrans
s1: 1362.6250 MB / 1.00 sec = 11430.9614 Mbps 0 retrans
s2: 1285.6875 MB / 1.00 sec = 10785.2147 Mbps 0 retrans
s1: 2107.5625 MB / 1.00 sec = 17679.3919 Mbps 0 retrans
s2: 2107.6250 MB / 1.00 sec = 17680.0930 Mbps 0 retrans
s1: 2108.0625 MB / 1.00 sec = 17683.6392 Mbps 0 retrans
s2: 2108.0625 MB / 1.00 sec = 17683.8161 Mbps 0 retrans
s1: 2107.0000 MB / 1.00 sec = 17674.9561 Mbps 0 retrans
s2: 2107.0000 MB / 1.00 sec = 17674.6557 Mbps 0 retrans
s1: 2094.6250 MB / 1.00 sec = 17571.0056 Mbps 0 retrans
s2: 2181.7500 MB / 1.00 sec = 18301.9736 Mbps 0 retrans
Original comment by bltier...@es.net
on 7 Nov 2013 at 3:41
We're using -L for the TCP flow label, so we'll have to come up with a
different flag for this. We could copy nuttcp and use -I, but how about -T /
--title? We're not using "title" anywhere in the code right now.
Also, I think I'll add the ": " punctuation automatically, so you only have to
specify a simple string. Looks like nuttcp does this too.
Original comment by jef.posk...@gmail.com
on 9 Nov 2013 at 12:21
Original comment by jef.posk...@gmail.com
on 9 Nov 2013 at 4:33
Original issue reported on code.google.com by
bltier...@es.net
on 5 Jun 2013 at 10:03