sys_basher

<body topmargin=0 leftmargin=0 marginheight=0 marginwidth=0> <table cellpadding=0 cellspacing=0 border=0><tr> <td valign="top" colspan=2 height=90 BGCOLOR="#CC9900" TEXT="#080000" bgproperties="fixed" background="044005a0dwnjzk.gif"> <div> <B>sys_basher</B></div> <bR> <div> </div> </td> </tr><tr> <td valign="top" width=210 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <B><IMG SRC="03f69830.gif" border=0 width="105" height="131" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></B></div> <div> <A HREF="http://www.polybus.com" TARGET="_top" TITLE="http://www.polybus.com"><U><B>Polybus Systems Corp</B></U></A></div> <div> <B>23 Providence Rd</B></div> <div> <B>Westford, MA 01886</B></div> <div> <B>(978) 828-0944</B></div> <bR> <div> <A HREF="http://www.polybus.com/ib_link_layer_website" TARGET="_top" TITLE="http://www.polybus.com/ib_link_layer_web"><U><B>InfiniBand Cores</B></U></A></div> </td> <td valign="top" height=390 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <B>Sys_basher is offered free of charge by Polybus Systems corporation under a BSD style open source</B><B> </B><A HREF="id17.htm" TARGET="_top" TITLE="License"><U><B>license</B></U></A><B>.</B></div> <div> <B>Polybus offers Intellectual Property including InfiniBand Link Layer and Transport Layer cores. Polybus also provides FPGA and ASIC design services.</B></div> <div> <B>Polybus is the leading supplier of InfiniBand cores for use in Xilinx Virtex2P, Virtex4FX, Virtex5FXT and Altera Stratix2GX and Stratix4GX FPGAs as well for ASICs. We offer an IBA Release 1.1 compliant Link Layer core (10GBit/Second), an IBA Release 1.2 compliant Double Data Rate Link Layer core (20GBit/Second), 1.2 compliant 8X QDR LInk Layer Cores  (80GBits/Sec) , and  SDR and DDR UC Target Channel Adapters.</B></div> <div> <A HREF="http://www.polybus.com/ib_link_layer_website" TARGET="_top" TITLE="http://www.polybus.com/ib_link_layer_web"><U>http://www.polybus.com/ib_link_layer_website</U></A>.</div> <bR> <div> <B>If you are looking for FPGA or ASIC design consulting or would like more information about our cores please contact Joshua Rosen </B><A HREF="mailto:bjrosen@polybus.com" TARGET="_top" TITLE="mailto:bjrosen@polybus.com"><U><B>bjrosen@polybus.com</B></U></A><B>, (978) 828-0944.</B></div> <bR> <div> <B>sys_basher may be downloaded here,</B></div> <div> <A HREF="http://www.polybus.com/sys_basher/sys_basher.tar.gz" TARGET="_top" TITLE="http://www.polybus.com/sys_basher/sys_ba"><U><B>sys_basher.tar.gz</B></U></A></div> <div> <A HREF="http://www.polybus.com/sys_basher/sys_basher.zip" TARGET="_top" TITLE="http://www.polybus.com/sys_basher/sys_ba"><U><B>sys_basher.zip</B></U></A></div> <bR> <div> Sys_basher is a multithreaded memory and disk exerciser. It's purpose is to provide a system reliablity test, it is not designed to identify individual failed components. Sys_basher can keep all the cores in a system running at 100% capacity using 100% of the memory bandwidth. The floating point tests use the FP multipliers, adders, and memory system at the maximum possible rate, this should heat the CPU as much as any application will. It is also capable of doing continuous disk I/O to upto 32 separate directories. </div> <bR> <div> Sys_basher is a 64 bit program, it should have no trouble running on systems with > 4G of RAM. If it is compiled on a 32 bit system it will only be able to test about 3G of RAM which is the limit imposed by the 32 bit Linux kernel. The program is POSIX compliant so it should work on any *nix system, although it's only been tested on Fedora  9,10, CentOS 5.2  and Cygwin on WinXP.</div> <bR> <div> Sys_basher can spawn multiple threads, each running the selected suite of tests. The default number of Cores supported is 16 however this number can be changed by modifying the MAX_CORES value in sys_structs.h and recompiling. The default number of threads is the number of CPUs in the system, the thread limit can be changed with the --threads switch which allows the user to specify from 1 to MAX_CORES threads.</div> <bR> <div> Sys_basher can test most of the physical memory on a system.  The default is to test only the free memory however a switch is provided which allows the user to set the test array size to the total memory size minus a specified number of megabytes. If the test array is set to totalmem - 300 MBytes, or smaller, the memory tests will usually  run without swapping. To increase the amount of memory that's testable it is suggested that you run at INIT 3 (no X) with no other programs running. </div> <bR> <div> As of rev 1.0.7 sys_basher logs CPU and system temperatures. The current temperatures are displayed after each test completes and a table of maximum temperatures is displayed at the end ot the test. Temperature logging is available for Linux only and requires the installation of lm-sensors and the libsensors development library.</div> <bR> <div> To run without swapping,</div> <bR> <div> sys_basher -totalmem 300</div> <bR> <div> If swapping is desired then set the reserve space to 0,</div> <bR> <div> sys_basher -totalmem 0</div> <bR> <div> ------------------------------------------------------------------------------------------------------------------</div> <div> <B>Building sys_basher. </B></div> <bR> <div> Sys_basher can be built with or without sensors. </div> <bR> <div> To build it with sensors you will have to install the libsensors development package.</div> <bR> <div> For Redhat and Clones     yum -y install lm_sensors-devel</div> <div> For Ubuntu          sudo apt-get libsensors-dev</div> <bR> <div> To build it without you will need to do a make nosensors instead of make or make sys_basher</div> <bR> <div> make sys_basher</div> <div> make nosensors    Make without lm-sensors</div> <div> make win          Make for Cygwin</div> <div> make install      Make sys_basher and move it to /usr/bin</div> <div> ------------------------------------------------------------------------------------------------------------------</div> <div> <B>Report Files</B></div> <bR> <div> Sys_basher generates a report in two formats, .rpt and .csv. The .rpt format is human readable text file format, .csv is a comma separated format thats allows the user to import the results into a spreadsheet.</div> <bR> <div> To generate the report files use the -r switch,</div> <bR> <div> sys_basher -r report</div> <div> ------------------------------------------------------------------------------------------------------------------</div> <div> <B>Verbosity control</B></div> <bR> <div> The default output from sys_basher is simple pass/fail status. The -v switch adds detailed test by test status results including the temperature after each test. The information in the verbose mode is also available in the report files so for healthy systems it is recommended that you don't use the -v switch. For unstable systems the verbose mode can be very useful in determining the source of the unreliability so for systems that crash it is recommended that the -v switch be used and that the output be redirected to a log file,</div> <bR> <div> sys_basher -v >& log </div> <bR> <div> ------------------------------------------------------------------------------------------------------------------</div> <div> <B>Running sys_basher</B></div> <div> sys_basher [options]</div> <bR> <div> options:</div> <div>   -d,--disk                   Run disk tests only</div> <div>   -du,--dutycyle              Dutycycle n Duty cycle in percent, the default is 100</div> <div>                               Inserts Sleeps between tests to reduce the overall CPU duty cycle</div> <div>   -f,--fast                   Skip the memory tests, just run the disk, fp and memory bandwidth tests.</div> <div>   -fp,--fp                    Run floating point tests only</div> <div>   -h,--help                   Print this help message</div> <div>   -ho #,--hours #             Run for at least # hours.</div> <div>   -i,--int                    Run integer tests only</div> <div>   -l #,--loops #              Number of iterations.</div> <div>   -mb,--mbandwidth            Run memory bandwidth only</div> <div>   -m,--mem                    Run memory tests only</div> <div>   -mi,--minutes #             Run for at least # minutes.</div> <div>   -p n0..nx,--path n0..nx     Directory path(s) for the disk tests, upto 32 paths maybe specified. The default path is ./</div> <div>   -r name,--report name       Report file name, generate name.rpt and name.csv. Default is not report</div> <div>   -s,--swap                   Force use of swap space. This option is incredibly slow.</div> <div>   -th,--threads n             Maximum number of threads. Spawn 1-n threads, the default is 2.</div> <div>   -t,--totalmem n             Allocate total ram - (n * 1M) for testing. If -totalmem is not called then the free space is used.</div> <div>   -v,--verbose                Verbose, print detailed results, default is PASS/FAIL only.</div> <div>   -ve,--version               Version number</div> <bR> <div> ------------------------------------------------------------------------------------------------------------------</div> <bR> <div> <B>Examples,</B></div> <bR> <div> Run benchmarks and fast tests only,</div> <bR> <div> sys_basher -fast >& log &</div> <bR> <div> Run two iterations, use totalmem - 256M, do disk tests on 2 partitions,</div> <bR> <div> sys_basher -loops 2 -path /fcx/projects /home/bjrosen -totalmem 256 >& log.$1 &</div> <bR> <div> Run for 8 hours, use totalmem - 256M, do disk tests on 4 partitions, set the maximum thread count to 4 and loop on the maximum threads</div> <bR> <div> sys_basher -hours 8 -th 4 -tm -path /fcw/projects /fcx/projects /fcx/projects /home/bjrosen  -totalmem 256 >& log.$1 &</div> <bR> <div> Force swapping,</div> <bR> <div> sys_basher -totalmem 0 >& log &</div> <bR> <div> ------------------------------------------------------------------------------------------------------------------</div> <div> <B>Revision History</B></div> <div> 1.0.1     First version</div> <div> 1.0.2     Added disk tests</div> <div> 1.0.3     Added No sync mode for disk tests in addition to the sync mode that was introduced into 1.0.2</div> <div>      Added -hours, -minutes and -path switches</div> <div>      Added floating point tests</div> <div>      Improved the output formatting</div> <div> 1.0.4     Added check to see that malloc succeeded. Fix FP Sum of Products tests.</div> <div>      There are some issues with the Disk Tests which will be addressed in the next rev. </div> <div>      If the disk tests fail DON'T PANIC, it's probably my code.</div> <div> 1.0.5     Fixed disk tests and improved FP tests.</div> <div> 1.0.6     Added duty cycle control.</div> <div> 1.0.7     Added CPU Temperature monitoring, Cygwin support</div> <div> 1.0.8     Added integer arithmetic tests. Fixed Cygwin bug.</div> <div> 1.0.9     Added -memonly</div> <div> 1.1.0     Added report files, added 16 bit integer tests, added verbose mode switch. Made the number of supported cores scalable</div> <div>           Cygwin version now does disk I/O and uses POSIX threads</div> <div> 1.1.1     Cleaned up the stdio output. Switches can be preceeded by either - or --. </div> <div>           Added transcript file, sys_basher.log</div> <div> 1.1.2     Added support for libsensors3</div> <div> 1.1.5     Added -tm switch which loops on the maximum number of threads. Improved memory tests. All integer and FP tests now </div> <div>           run for a minimum of .5 seconds. The default number of threads is set to the number of CPUs.</div> <div> 1.1.6     A little cleanup in the report file, no test or feature changes.</div> <bR> </td> </tr></table></body>