History log of /freebsd-12.1/tools/tools/netrate/tcpp/tcpp.h (Results 1 – 3 of 3)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0, release/7.4.0, release/8.2.0, release/8.1.0
# 698337f6 06-Jun-2010 Robert Watson <[email protected]>

Rework tcpp output so that it generates a comma-delimited list of values,
optionally with a header if "-h" is passed. Toast CPU time measurement
in the server for now. Remove -C and -T, since we no

Rework tcpp output so that it generates a comma-delimited list of values,
optionally with a header if "-h" is passed. Toast CPU time measurement
in the server for now. Remove -C and -T, since we now always report
both connections/sec and Gb/sec.

MFC after: 1 week
Sponsored by: Juniper Networks

show more ...


# 73dd1f43 05-Jun-2010 Robert Watson <[email protected]>

Although we currently don't compile in CPU-pinning support by default,
add a -P to enable it if it were.

MFC after: 1 week
Sponsored by: Juniper Networks


Revision tags: release/7.3.0, release/8.0.0, release/7.2.0
# b860cb26 10-Mar-2009 Robert Watson <[email protected]>

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 mul

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.

show more ...