Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3 |
|
#
944cd60c |
| 25-Sep-2019 |
Sascha Wildner <saw@online.de> |
<sys/time.h>: Add 3rd arg to timespecadd()/sub() and make them public.
* Switch to the three argument versions of the timespecadd() and timespecsub() macros. These are now the predominant ones. Fr
<sys/time.h>: Add 3rd arg to timespecadd()/sub() and make them public.
* Switch to the three argument versions of the timespecadd() and timespecsub() macros. These are now the predominant ones. FreeBSD, OpenBSD, NetBSD, and Solaris (albeit only for the kernel) have them.
* Make those macros public too. This allows for a number of cleanups where they were defined locally.
Pointed-out-by: zrj Reviewed-by: dillon
show more ...
|
Revision tags: v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc |
|
#
12439f34 |
| 18-Jan-2017 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
tools/kq_sendrecv: Fix building on FreeBSD
|
#
2fe73a22 |
| 17-Jan-2017 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
tools/kq_sendcli: Add option to set sending thread's CPU affinity
|
#
a06d7982 |
| 17-Jan-2017 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
tool/kq_sendcli: Add option to set write size.
|
#
dbeb2594 |
| 17-Jan-2017 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
tools/kq_sendcli: Add sendfile support.
Based on work done by QianYue You.
|
Revision tags: v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3 |
|
#
772669ff |
| 30-Mar-2016 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
tools/kq_sendrecv: Implement kqueue(2) based TCP traffic generator
It is mainly used to genetate TCP traffic w/ large amount of TCP connections, e.g. > 10K connections. netperf is no longer suitabl
tools/kq_sendrecv: Implement kqueue(2) based TCP traffic generator
It is mainly used to genetate TCP traffic w/ large amount of TCP connections, e.g. > 10K connections. netperf is no longer suitable to generate this kind of TCP traffic, since 10K+ processes is not desirable. iperf3 is also not suitable, since it is implemented using select(2).
show more ...
|