214145 |
21-Oct-2010 |
rwatson |
Fix bug in recent syscall_timing change: measure the number of iterations each loop, rather than once up front. The distinction is unimportant when doing a fix iteration count, but when using a timer, it should vary.
Sponsored by: Google, Inc. MFC after: 2 weeks
|
214142 |
21-Oct-2010 |
rwatson |
Further enhancements to syscall_timing:
- Use getopt rather than hand-parsed arguments - Allow iterations to be specified and/or a new number of seconds bound on the number of iterations - Fix printout of timer resolution - Add new tests, such as TCP and UDP socket creation, and open/read/close of /dev/zero and /dev/null.
Sponsored by: Google, Inc. MFC after: 2 weeks
|
214135 |
21-Oct-2010 |
rwatson |
Improve the structure and implementation of the syscall_timing microbenchmark suite:
- Use common benchmark_start/benchmark_stop routines to simplify individual benchmarks. - Add a central table of tests with names, where new tests can be hooked in easily. - Add new benchmarks for dup, shm_open, shm_open + fstat, fork, vfork, vfork + exec, chroot, setuid. - Accept a number of loops, not just a number of iterations. - Report results more usefully in a table.
Sponsored by: Google, Inc. MFC after: 2 weeks
|