Date: Thu, 26 Aug 2010 21:37:21 +0000 (UTC) From: Jeff Roberson <jeff@FreeBSD.org> To: src-committers@freebsd.org, svn-src-projects@freebsd.org Subject: svn commit: r211850 - in projects/ofed/base/contrib/ofed/qperf: . src Message-ID: <201008262137.o7QLbLwH054321@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: jeff Date: Thu Aug 26 21:37:20 2010 New Revision: 211850 URL: http://svn.freebsd.org/changeset/base/211850 Log: - Import qperf from git://git.openfabrics.org/~johann/qperf.git/.git rev b81434ec094694bae55e20dd1af5f5057d8e5f82 Sponsored by: Isilon Systems, iX Systems, and Panasas Added: projects/ofed/base/contrib/ofed/qperf/ projects/ofed/base/contrib/ofed/qperf/AUTHORS projects/ofed/base/contrib/ofed/qperf/COPYING projects/ofed/base/contrib/ofed/qperf/Makefile.am projects/ofed/base/contrib/ofed/qperf/README projects/ofed/base/contrib/ofed/qperf/autogen.sh (contents, props changed) projects/ofed/base/contrib/ofed/qperf/cleanup (contents, props changed) projects/ofed/base/contrib/ofed/qperf/configure.in projects/ofed/base/contrib/ofed/qperf/qperf.spec projects/ofed/base/contrib/ofed/qperf/qperf.spec.in projects/ofed/base/contrib/ofed/qperf/src/ projects/ofed/base/contrib/ofed/qperf/src/Makefile.am projects/ofed/base/contrib/ofed/qperf/src/help.txt projects/ofed/base/contrib/ofed/qperf/src/mkhelp (contents, props changed) projects/ofed/base/contrib/ofed/qperf/src/mkman (contents, props changed) projects/ofed/base/contrib/ofed/qperf/src/qperf.c projects/ofed/base/contrib/ofed/qperf/src/qperf.h projects/ofed/base/contrib/ofed/qperf/src/rdma.c projects/ofed/base/contrib/ofed/qperf/src/rds.c projects/ofed/base/contrib/ofed/qperf/src/socket.c projects/ofed/base/contrib/ofed/qperf/src/support.c Added: projects/ofed/base/contrib/ofed/qperf/AUTHORS ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/AUTHORS Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,7 @@ +Written by Johann George + +Thanks to the following for their contributions: + Dotan Barak + Ralph Campbell + Yevgeny Kliteynik + Dave Olson Added: projects/ofed/base/contrib/ofed/qperf/COPYING ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/COPYING Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Lesser General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License along + with this program; if not, write to the Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + <signature of Ty Coon>, 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. Added: projects/ofed/base/contrib/ofed/qperf/Makefile.am ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/Makefile.am Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,6 @@ +SUBDIRS = src + +EXTRA_DIST = qperf.spec.in + +dist-hook: qperf.spec + cp qperf.spec $(distdir) Added: projects/ofed/base/contrib/ofed/qperf/README ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/README Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,18 @@ +To build + ./cleanup + ./autogen.sh + ./configure + make + +Changing version + * src/qperf.c: Change VER_MAJ, VER_MIN and VER_INC. + * configure.in: Change in AC_INIT and AM_INIT_AUTOMAKE + * qperf.spec: Change line beginning with Version: + * Note ensure that qperf.spec is modified last so that cleanup does not + delete it. + +Notes + * If the library ibverbs is not found, a version of qperf is built that + does not support the RDMA tests. + * Running "make clean" does not seem to clean up everything. Run + "./cleanup" instead. Added: projects/ofed/base/contrib/ofed/qperf/autogen.sh ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/autogen.sh Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,9 @@ +#!/bin/sh + +set -x +for f in NEWS README ChangeLog; do + [ -e "$f" ] || touch "$f" +done +aclocal && + automake --foreign --add-missing --copy && + autoconf Added: projects/ofed/base/contrib/ofed/qperf/cleanup ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/cleanup Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,38 @@ +#!/bin/sh +# autotools makes such a mess. Clean up after it. +# +for f in AUTHORS NEWS README ChangeLog; do + [ -s "$f" ] || rm -f "$f" +done +rm -r -f autom4te.cache .deps src/.deps +rm -f `cat <<EOF + INSTALL + Makefile + Makefile.in + aclocal.m4 + config.log + config.status + configure + depcomp + install-sh + missing + src/Makefile + src/Makefile.in + src/*.o + src/help.c + src/qperf.1 + src/qperf +EOF` + +# We need to keep qperf.spec around for the OFED scripts but delete it if we do +# not think it is correct. This might be due to three reasons: (1) it does not +# represent the RDMA version, (2) qperf.spec.in is newer and (3) configure.in +# is newer. +# +if + ! grep -q -s '^BuildRequires: *libibverbs-devel' qperf.spec || + [ qperf.spec.in -nt qperf.spec ] || + [ configure.in -nt qperf.spec ] +then + rm -f qperf.spec +fi Added: projects/ofed/base/contrib/ofed/qperf/configure.in ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/configure.in Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,8 @@ +AC_INIT(qperf, 0.4.6, general@lists.openfabrics.org) +AM_INIT_AUTOMAKE(qperf, 0.4.6) +AC_PROG_CC +AC_CHECK_LIB(ibverbs, ibv_open_device, RDMA=1) +AC_CHECK_LIB(rdmacm, rdma_create_id) +AM_CONDITIONAL(RDMA, test -n "$RDMA") +AC_CONFIG_FILES([qperf.spec]) +AC_OUTPUT(Makefile src/Makefile) Added: projects/ofed/base/contrib/ofed/qperf/qperf.spec ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/qperf.spec Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,38 @@ +Name: qperf +Summary: Measure socket and RDMA performance +Version: 0.4.6 +Release: 1 +License: BSD 3-Clause, GPL v2 +Group: Networking/Diagnostic +Source: http://www.openfabrics.org/downloads/qperf-0.4.6.tar.gz +Url: http://www.openfabrics.org +BuildRoot: %{_tmppath}/%{name}-%{version}-build +BuildRequires: libibverbs-devel + +%description +Measure socket and RDMA performance. + +%prep +%setup -q + +%build +%configure +export CFLAGS="$RPM_OPT_FLAGS" +%{__make} + +%install +install -D -m 0755 src/qperf $RPM_BUILD_ROOT%{_bindir}/qperf +install -D -m 0644 src/qperf.1 $RPM_BUILD_ROOT%{_mandir}/man1/qperf.1 + +%clean +rm -rf ${RPM_BUILD_ROOT} + +%files +%defattr(-, root, root) +%doc COPYING +%_bindir/qperf +%_mandir/man1/qperf.1* + +%changelog +* Sat Oct 20 2007 - johann@georgex.org +- Initial package Added: projects/ofed/base/contrib/ofed/qperf/qperf.spec.in ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/qperf.spec.in Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,38 @@ +Name: qperf +Summary: Measure socket and RDMA performance +Version: @VERSION@ +Release: 1 +License: BSD 3-Clause, GPL v2 +Group: Networking/Diagnostic +Source: http://www.openfabrics.org/downloads/%{name}-%{version}.tar.gz +Url: http://www.openfabrics.org +BuildRoot: %{_tmppath}/%{name}-%{version}-build +@RDMA_TRUE@BuildRequires: libibverbs-devel + +%description +Measure socket and RDMA performance. + +%prep +%setup -q + +%build +%configure +export CFLAGS="$RPM_OPT_FLAGS" +%{__make} + +%install +install -D -m 0755 src/qperf $RPM_BUILD_ROOT%{_bindir}/qperf +install -D -m 0644 src/qperf.1 $RPM_BUILD_ROOT%{_mandir}/man1/qperf.1 + +%clean +rm -rf ${RPM_BUILD_ROOT} + +%files +%defattr(-, root, root) +%doc COPYING +%_bindir/qperf +%_mandir/man1/qperf.1* + +%changelog +* Sat Oct 20 2007 - johann@georgex.org +- Initial package Added: projects/ofed/base/contrib/ofed/qperf/src/Makefile.am ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/src/Makefile.am Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,25 @@ +bin_PROGRAMS = qperf + +if RDMA +AM_CFLAGS = -Wall -O -DRDMA +qperf_SOURCES = qperf.c socket.c rds.c rdma.c support.c help.c qperf.h +qperf_LDADD = -libverbs +else +AM_CFLAGS = -Wall -O +qperf_SOURCES = qperf.c socket.c rds.c support.c help.c qperf.h +endif + +man_MANS = qperf.1 + +qperf.1: help.txt + ./mkman >qperf.1 + +help.c: help.txt +if RDMA + ./mkhelp RDMA +else + ./mkhelp +endif + +clean-local: + -rm -f qperf.1 Added: projects/ofed/base/contrib/ofed/qperf/src/help.txt ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/ofed/base/contrib/ofed/qperf/src/help.txt Thu Aug 26 21:37:20 2010 (r211850) @@ -0,0 +1,979 @@ +Main + Synopsis + qperf + qperf SERVERNODE [OPTIONS] TESTS + + Description + qperf measures bandwidth and latency between two nodes. It can work + over TCP/IP as well as the RDMA transports. On one of the nodes, qperf + is typically run with no arguments designating it the server node. One + may then run qperf on a client node to obtain measurements such as + bandwidth, latency and cpu utilization. + + In its most basic form, qperf is run on one node in server mode by + invoking it with no arguments. On the other node, it is run with two + arguments: the name of the server node followed by the name of the + test. A list of tests can be found in the section, TESTS. A variety + of options may also be specified. + + One can get more detailed information on qperf by using the --help + option. Below are examples of using the --help option: + + qperf --help examples Some examples of using qperf + qperf --help opts Summary of options + qperf --help options Description of options + qperf --help tests Short summary and description of tests + qperf --help TESTNAME More information on test TESTNAME +Author + Written by Johann George. +Bugs + None of the RDMA tests are available if qperf is compiled without the RDMA + libraries. The -f option is not yet implemented in many of the tests. +Categories -RDMA + To get help on a particular category, you may type: + qperf --help CATEGORY + where CATEGORY might be one of the following: + categories This current list being displayed + examples Some examples + options A long list of options + opts A short description of the options + tests A list and description of the various tests + or one of the following tests: + conf + quit + rds_bw + rds_lat + sctp_bw + sctp_lat + sdp_bw + sdp_lat + tcp_bw + tcp_lat + udp_bw + udp_lat +Categories +RDMA + To get help on a particular category, you may type: + qperf --help CATEGORY + where CATEGORY might be one of the following: + categories This current list being displayed + examples Some examples + options A long list of options + opts A short description of the options + tests A list of tests + CATEGORY may also be one of the following tests + conf + quit + rc_bi_bw + rc_bw + rc_compare_swap_mr + rc_fetch_add_mr + rc_lat + rc_rdma_read_bw + rc_rdma_read_lat + rc_rdma_write_bw + rc_rdma_write_lat + rc_rdma_write_poll_lat + rds_bw + rds_lat + sctp_bw + sctp_lat + sdp_bw + sdp_lat + tcp_bw + tcp_lat + uc_bi_bw + uc_bw + uc_lat + uc_rdma_write_bw + uc_rdma_write_lat + uc_rdma_write_poll_lat + ud_bi_bw + ud_bw + ud_lat + udp_bw + udp_lat + ver_rc_compare_swap + ver_rc_fetch_add + xrc_bi_bw + xrc_bw + xrc_lat +Examples + In these examples, we first run qperf on a node called myserver in server + mode by invoking it with no arguments. In all the subsequent examples, we + run qperf on another node and connect to the server which we assume has a + hostname of myserver. + * To run a TCP bandwidth and latency test: + qperf myserver tcp_bw tcp_lat + * To run a SDP bandwidth test for 10 seconds: + qperf myserver -t 10 sdp_bw + * To run a UDP latency test and then cause the server to terminate: + qperf myserver udp_lat quit + * To measure the RDMA UD latency and bandwidth: + qperf myserver ud_lat ud_bw + * To measure RDMA UC bi-directional bandwidth: + qperf myserver rc_bi_bw + * To get a range of TCP latencies with a message size from 1 to 64K + qperf myserver -oo msg_size:1:64K:*2 -vu tcp_lat +Opts + --access_recv OnOff (-ar) Turn on/off accessing received data + -ar1 Cause received data to be accessed + --alt_port Port (-ap) Set alternate path port + --loc_alt_port Port (-lap) Set local alternate path port + --rem_alt_port Port (-rap) Set remote alternate path port + --cpu_affinity PN (-ca) Set processor affinity + --loc_cpu_affinity PN (-lca) Set local processor affinity + --rem_cpu_affinity PN (-rca) Set remote processor affinity + --flip OnOff (-f) Flip on/off sender and receiver + -f1 Flip (on) sender and receiver + --help Topic (-h) Get more information on a topic + --host Node (-H) Identify server node + --id Device:Port (-i) Set RDMA device and port + --loc_id Device:Port (-li) Set local RDMA device and port + --rem_id Device:Port (-ri) Set remote RDMA device and port + --listen_port Port (-lp) Set server listen port + --loop Var:Init:Last:Incr (-oo) Sequence through values + --msg_size Size (-m) Set message size + --mtu_size Size (-mt) Set MTU size (RDMA only) + --no_msgs Count (-n) Send Count messages + --cq_poll OnOff Set polling mode on/off + --loc_cq_poll OnOff (-lcp) Set local polling mode on/off + --rem_cq_poll OnOff (-rcp) Set remote polling mode on/off + -cp1 Turn polling mode on + -lcp1 Turn local polling mode on + -rcp1 Turn remote polling mode on + --ip_port Port (-ip) Set TCP port used for tests + --precision Digits (-e) Set precision reported + --rd_atomic Max (-nr) Set RDMA read/atomic count + --loc_rd_atomic Max (-lnr) Set local RDMA read/atomic count + --rem_rd_atomic Max (-rnr) Set remote RDMA read/atomic count + --service_level SL (-sl) Set service level + --service_level SL (-lsl) Set local service level + --service_level SL (-rsl) Set remote service level + --sock_buf_size Size (-sb) Set socket buffer size + --loc_sock_buf_size Size (-lsb) Set local socket buffer size + --rem_sock_buf_size Size (-rsb) Set remote socket buffer size + --src_path_bits num (-sp) Set source path bits + --loc_src_path_bits num (-lsp) Set local source path bits + --rem_src_path_bits num (-rsp) Set remote source path bits + --static_rate (-sr) Set IB static rate + --loc_static_rate (-lsr) Set local IB static rate + --rem_static_rate (-rsr) Set remote IB static rate + --time Time (-t) Set test duration + --timeout Time (-to) Set timeout + --loc_timeout Time (-lto) Set local timeout + --rem_timeout Time (-rto) Set remote timeout + --unify_nodes (-un) Unify nodes + --unify_units (-uu) Unify units + --use_bits_per_sec (-ub) Use bits/sec rather than bytes/sec + --use_cm OnOff (-cm) Use RDMA Connection Manager or not + -cm1 Use RDMA Connection Manager + --verbose (-v) Verbose; turn on all of -v[cstu] + --verbose_conf (-vc) Show configuration information + --verbose_stat (-vs) Show statistical information + --verbose_time (-vt) Show timing information + --verbose_used (-vu) Show information on parameters + --verbose_more (-vv) More verbose; turn on all of -v[CSTU] + --verbose_more_conf (-vvc) Show more configuration information + --verbose_more_stat (-vvs) Show more statistical information + --verbose_more_time (-vvt) Show more timing information + --verbose_more_used (-vvu) Show more information on parameters + --version (-V) Print out version + --wait_server Time (-ws) Set time to wait for server +Options + --access_recv OnOff (-ar) + If OnOff is non-zero, data is accessed once received. Otherwise, + data is ignored. By default, OnOff is 0. This can help to mimic + some applications. + -ar1 + Cause received data to be accessed. + --alt_port Port (-ap) + Set alternate path port. This enables automatic path failover. + --loc_alt_port Port (-lap) + Set local alternate path port. This enables automatic path failover. + --rem_alt_port Port (-rap) + Set remote alternate path port. This enables automatic path failover. + --cpu_affinity PN (-ca) + Set cpu affinity to PN. CPUs are numbered sequentially from 0. If + PN is "any", any cpu is allowed otherwise the cpu is limited to the + one specified. + --loc_cpu_affinity PN (-lca) + Set local processor affinity to PN. + --rem_cpu_affinity PN (-rca) + Set remote processor affinity to PN. + --flip OnOff (-f) + If non-zero, cause sender and receiver to play opposite roles. + -f1 + Cause sender and receiver to play opposite roles. + --help Topic (-h) + Print out information about Topic. To see the list of topics, type + qperf --help + --host Host (-H) + Run test between the current node and the qperf running on node Host. + This can also be specified as the first non-option argument. + --id Device:Port (-i) + Use RDMA Device and Port. + --loc_id Device:Port (-li) + Use local RDMA Device and Port. + --rem_id Device:Port (-ri) + Use remote RDMA Device and Port. + --listen_port Port (-lp) + Set the port we listen on to ListenPort. This must be set to the + same port on both the server and client machines. The default value + is 19765. + --loop Var:Init:Last:Incr (-oo) + Run a test multiple times sequencing through a series of values. Var + is the loop variable; Init is the initial value; Last is the value it + must not exceed and Incr is the increment. It is useful to set the + --verbose_used (-vu) option in conjunction with this option. + --msg_size Size (-m) + Set the message size to Size. The default value varies by test. It + is assumed that the value is specified in bytes however, a trailing + kib or K, mib or M, or gib or G indicates that the size is being + specified in kibibytes, mebibytes or gibibytes respectively while a + trailing kb or k, mb or m, or gb or g indicates kilobytes, megabytes + or gigabytes respectively. + --mtu_size Size (-mt) + Set the MTU size. Only relevant to the RDMA UC/RC tests. Units are + specified in the same manner as the --msg_size option. + --no_msgs N (-n) + Set test duration by number of messages sent instead of time. + --cq_poll OnOff (-cp) + Turn polling mode on or off. This is only relevant to the RDMA tests + and determines whether they poll or wait on the completion queues. + If OnOff is 0, they wait; otherwise they poll. + --loc_cq_poll OnOff (-lcp) + Locally turn polling mode on or off. + --rem_cq_poll OnOff (-rcp) + Remotely turn polling mode on or off. + -cp1 + Turn polling mode on. + -lcp1 + Turn local polling mode on. + -rcp1 + Turn remote polling mode on. + --ip_port Port (-ip) + Use Port to run the socket tests. This is different from + --listen_port which is used for synchronization. This is only + relevant for the socket tests and refers to the TCP/UDP/SDP/RDS/SCTP + port that the test is run on. + --precision Digits (-e) + Set the number of significant digits that are used to report results. + --rd_atomic Max (-nr) + Set the number of in-flight operations that can be handled for a RDMA + read or atomic operation to Max. This is only relevant to the RDMA + Read and Atomic tests. + --loc_rd_atomic Max (-lnr) + Set local read/atomic count. + --rem_rd_atomic Max (-rnr) + Set remote read/atomic count. + --service_level SL (-sl) + Set RDMA service level to SL. This is only used by the RDMA tests. + The service level must be between 0 and 15. The default service + level is 0. + --loc_service_level SL (-lsl) + Set local service level. + --rem_service_level SL (-rsl) + Set remote service level. + --sock_buf_size Size (-sb) + Set the socket buffer size. This is only relevant to the socket + tests. + --loc_sock_buf_size Size (-lsb) + Set local socket buffer size. + --rem_sock_buf_size Size (-rsb) + Set remote socket buffer size. + --src_path_bits N (-sp) + Set source path bits. If the LMC is not zero, this will cause the + connection to use a LID with the low order LMC bits set to N. + --loc_src_path_bits N (-lsp) + Set local source path bits. + --rem_src_path_bits N (-rsp) + Set remote source path bits. + --static_rate Rate (-sr) + Force InfiniBand static rate. Rate can be one of: 2.5, 5, 10, 20, + 30, 40, 60, 80, 120, 1xSDR (2.5 Gbps), 1xDDR (5 Gbps), 1xQDR (10 + Gbps), 4xSDR (2.5 Gbps), 4xDDR (5 Gbps), 4xQDR (10 Gbps), 8xSDR (2.5 + Gbps), 8xDDR (5 Gbps), 8xQDR (10 Gbps). + --loc_static_rate (-lsr) + Force local InfiniBand static rate + --rem_static_rate (-rsr) + Force remote InfiniBand static rate + --time Time (-t) + Set test duration to Time. Specified in seconds however a trailing + m, h or d indicates that the time is specified in minutes, hours or + days respectively. + --timeout Time (-to) + Set timeout to Time. This is the timeout used for various things + such as exchanging messages. The default is 5 seconds. + --loc_timeout Time (-lto) + Set local timeout to Time. This may be used on the server to set + the timeout when initially exchanging data with each client. + However, as soon as we receive the client's parameters, the client's + remote timeout will override this parameter. + --rem_timeout Time (-rto) + Set remote timeout to Time. + --unify_nodes (-un) + Unify the nodes. Describe them in terms of local and remote rather + than send and receive. + --unify_units (-uu) + Unify the units that results are shown in. Uses the lowest common + denominator. Helpful for scripts. + --use_bits_per_sec (-ub) + Use bits/sec rather than bytes/sec when displaying networking speed. + --use_cm OnOff (-cm) + Use the RDMA Connection Manager (CM) if OnOff is non-zero. It is + necessary to use the CM for iWARP devices. The default is to + establish the connection without using the CM. This only works for + the tests that use the RC transport. + -cm1 + Use RDMA Connection Manager. + --verbose (-v) + Provide more detailed output. Turns on -vc, -vs, -vt and -vu. + --verbose_conf (-vc) + Provide information on configuration. + --verbose_stat (-vs) + Provide information on statistics. + --verbose_time (-vt) + Provide information on timing. + --verbose_used (-vu) + Provide information on parameters used. + --verbose_more (-vv) + Provide even more detailed output. Turns on -vvc, -vvs, -vvt and + -vvu. + --verbose_more_conf (-vvc) + Provide more information on configuration. + --verbose_more_stat (-vvs) + Provide more information on statistics. + --verbose_more_time (-vvt) + Provide more information on timing. + --verbose_more_used (-vvu) + Provide more information on parameters used. + --version (-V) + The current version of qperf is printed. + --wait_server Time (-ws) + If the server is not ready, continue to try connecting for Time + seconds before giving up. The default is 5 seconds. +Tests -RDMA + Miscellaneous + conf Show configuration + quit Cause the server to quit + Socket Based + rds_bw RDS streaming one way bandwidth + rds_lat RDS one way latency + sctp_bw SCTP streaming one way bandwidth + sctp_lat SCTP one way latency + sdp_bw SDP streaming one way bandwidth + sdp_lat SDP one way latency + tcp_bw TCP streaming one way bandwidth + tcp_lat TCP one way latency + udp_bw UDP streaming one way bandwidth + udp_lat UDP one way latency +Tests +RDMA + Miscellaneous + conf Show configuration + quit Cause the server to quit + Socket Based + rds_bw RDS streaming one way bandwidth + rds_lat RDS one way latency + sctp_bw SCTP streaming one way bandwidth + sctp_lat SCTP one way latency + sdp_bw SDP streaming one way bandwidth + sdp_lat SDP one way latency + tcp_bw TCP streaming one way bandwidth + tcp_lat TCP one way latency + udp_bw UDP streaming one way bandwidth + udp_lat UDP one way latency + RDMA Send/Receive + rc_bi_bw RC streaming two way bandwidth + rc_bw RC streaming one way bandwidth + rc_lat RC one way latency + uc_bi_bw UC streaming two way bandwidth + uc_bw UC streaming one way bandwidth + uc_lat UC one way latency + ud_bi_bw UD streaming two way bandwidth + ud_bw UD streaming one way bandwidth + ud_lat UD one way latency + xrc_bi_bw XRC streaming two way bandwidth + xrc_bw XRC streaming one way bandwidth + xrc_lat XRC one way latency + RDMA + rc_rdma_read_bw RC RDMA read streaming one way bandwidth + rc_rdma_read_lat RC RDMA read one way latency + rc_rdma_write_bw RC RDMA write streaming one way bandwidth + rc_rdma_write_lat RC RDMA write one way latency + rc_rdma_write_poll_lat RC RDMA write one way polling latency + uc_rdma_write_bw UC RDMA write streaming one way bandwidth + uc_rdma_write_lat UC RDMA write one way latency + uc_rdma_write_poll_lat UC RDMA write one way polling latency + InfiniBand Atomics + rc_compare_swap_mr RC compare and swap messaging rate + rc_fetch_add_mr RC fetch and add messaging rate + Verification + ver_rc_compare_swap Verify RC compare and swap + ver_rc_fetch_add Verify RC fetch and add +conf + Purpose + Show configuration + Common Options + None + Description + Shows the node name, CPUs and OS of both nodes being used. +quit + Purpose + Quit + Common Options + None + Description + Causes the server to quit. +rds_bw + Purpose + RDS streaming one way bandwidth + Common Options + --access_recv OnOff (-ar) Access received data + --cpu_affinity PN (-ca) Set processor affinity + --msg_size Size (-m) Set message size + --sock_buf_size Size (-sb) Set socket buffer size + --time (-t) Set test duration + Other Options + --listen_port, --ip_port, --timeout + Display Options + --precision, --unify_nodes, --unify_units, --use_bits_per_sec, + --verbose + Description *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201008262137.o7QLbLwH054321>