freebsd-src/tools
Robert Watson b860cb2652 Add tcpp -- TCP parallelism microbenchmark.
This tool creates large numbers of TCP connections, each of which will
transmit a fixed amount of data, between client and server hosts.  tcpp can
use multiple workers (typically up to the number of hardware cores), and can
use multiple source IPs in order to use an expanded port/IP 4-tuple space to
avoid problems from reusing 4-tuples too quickly.  Aggregate bandwidth use
will be reported after a client run.

While by no means a perfect tool, it has proven quite useful in generating
and optimizing TCP stack lock contention by easily generating high-intensity
workloads.  It also proves surprisingly good at finding device driver bugs.
2009-03-10 14:52:17 +00:00
..
build Doh! r188813 modified an auto-generated file. Fix it for real: 2009-02-20 11:09:55 +00:00
debugscripts o Correct comments: remove a reference to non-existent gdbinit.9 man page; 2006-05-22 07:12:25 +00:00
diag Start the dreaded NOFOO -> NO_FOO conversion. 2004-12-21 08:47:35 +00:00
kerneldoc Remove ISDN4BSD (I4B) from HEAD as it is not MPSAFE and 2008-05-26 10:40:09 +00:00
KSE Start the dreaded NOFOO -> NO_FOO conversion. 2004-12-21 08:47:35 +00:00
LibraryReport
regression Rename files that collide on case-insensitive file systems by encoding 2009-03-10 09:33:22 +00:00
sched - Update my copyright. 2009-01-22 06:21:30 +00:00
test This is simple testing program for revision 185647. 2008-12-06 13:23:53 +00:00
tools Add tcpp -- TCP parallelism microbenchmark. 2009-03-10 14:52:17 +00:00
install.sh Arguments to options aren't necessarily separated with whitespace. 2004-07-07 09:38:14 +00:00
make_libdeps.sh - Add cddl/lib to the list of library directories. 2007-10-01 18:11:43 +00:00
README

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.