Lines Matching refs:netperf
1 These are the Release Notes for Revision 2.7.0 of netperf:
9 *) Much of the now-seeming kruft for things peripheral to netperf's
18 These are the Release Notes for Revision 2.6.0 of netperf:
24 <interval> option netperf will make sure it emits "one last
39 queue of the egress interface. This will help preclude netperf's
45 *) A new global -Z option has been added to netperf and netserver.
53 attempted receipt of the request message. In the case of netperf,
111 has been run as a non-spawning (-f) server, netperf has been run,
114 These are the Release Notes for Revision 2.5.0 of netperf:
139 netperf side of the "classic" netperf tests, and will also affect
144 Ostensibly, this may help when netperf is (ab)used in functional
198 Many, MANY concurrent netperf tests. Based on patches from Google.
231 *) Fixes to allow netperf -H ::1 to work without having to add -6 or
234 These are the Release Notes for Revision 2.4.5 of netperf:
246 *) Changes to enable compilation and building of netperf for
276 doc/netperf.texi in emacs texinfo mode and updating nodes and links
282 and netperf will emit a list of the known available outputs.
291 database of netperf results.
316 The idea is that this might be useful for netperf scripts wanting
328 These are the Release Notes for Revision 2.4.4 of netperf:
386 notice in future versions of netperf.
402 *) A new global, command-line option to netperf and netserver has been
403 added. The -V option will cause netperf/netserver to display its
414 These are the Release Notes for Revision 2.4.3 of netperf:
429 option will tell netperf to not bother to try to establish a
430 control connection with a remote netserver. Instead, netperf will
445 which _may_ mean that a future release of netperf may have
493 These are the Release Notes for Revision 2.4.2 of netperf:
521 These are the Release Notes for Revision 2.4.1 of netperf:
565 milliseconds for backwards compatability with previous netperf
571 These are the Release Notes for Revision 2.4.1 of netperf:
606 *) it is known that netperf will compile under Windows XP and 2003
607 using the DDK it is possible that netperf 2.4.1 will compile on a
616 These are the Release Notes for Revision 2.4.0 of netperf:
621 girls, after 12 years of distributing netperf with just a makefile
623 automake, etc. To get the most basic netperf built all you should
626 cd to the netperf directory
645 netperf manual has begun, with the source being a texinfo document
681 So, do NOT trust any CPU util figures where netperf says the method
685 accounting similar to what netperf uses on HP-UX 11.23. HOWEVER,
710 "0" so one must specify a port number on the netperf command line.
716 far as netperf goes :)
721 with --enable-demo when configuring netperf, which activates a
724 netperf's perspective to be emitted no sooner than once per second.
791 infinite loop when you abort netperf. I'm sure there are others.
805 These are the Release Notes for Revision 2.3pl2 of netperf:
809 *) One can bind netperf or netserver to specific CPUs with the -T
822 These are the Release Notes for revision 2.3pl1 of netperf:
837 These are the Release Notes for revision 2.3 of netperf:
843 support those folks who want to run netperf through those evil,
847 pre-2.3 netperf and netserver, it is not supported.
851 support those folks who want to run netperf through those evil,
855 pre-2.3 netperf and netserver, it is not supported.
885 These are the Release Notes for revision 2.2pl5 of netperf:
898 These are the Release Notes for Revision 2.2pl4 of netperf:
914 These are the Release Notes for revisoin 2.2pl3 of netperf:
923 details on what is involved in compiling and running netperf under
953 the data flows from the netserver to the netperf rather than from
954 the netperf to the netserver. This can be useful in those
955 situations where netperf (netserver) is installed on a remote
957 performance data for the path from netserver to netperf.
959 These are the Release Notes for the 2.2 revision of netperf:
992 These are the Release Notes for the 2.1pl3 revision of netperf:
1014 These are the Release Notes for the 2.1 revision of netperf:
1061 *) For accurate reporting of service demand, netperf needs to know the
1064 <numcpu>" option to both netperf and netserver.