simple disk benchmark

There is a minor bug in version 0.7: if first the "normal" throughput for large files with a big block size was calculated and then IOPS calculations were made, the measurement of the time was wrong. The time for both was used to calculate the throughput, which was wrong.
If you measure them both separately, the values are correct.

IOPS calculation is now possible. Thread synchronization was rewritten: it is more critical in order to calculate IOPS with several threads, the limit on the number of parallel threads is removed, and the output in verbose mode gives more information. CPU usage is calculated.

The second buffer is now initialized with memset() before memcpy(). This fixes the strange differences between memcpy() and bcopy(). Now -F activates the fsync() call after file operation. This release tries to find out the I/O scheduler being used and print it. /etc/mtab is used to find devices and filesystems instead of /proc/mounts. Some information from uname is printed in verbose mode as well as some timing values, maximum throughput, and the ideal one (maximum*threads). The load of the system is noted right before and after the real benchmark.

There is no functional change in this release. The verbose output is reformatted, users can add comments, and the hostname and date/time are printed. This release tries to find the device where the files reside and the used filesystem (maybe someone forgot to mount the drive?). The comment is helpful to include if, for example, someone changes the Cache from WriteBack to WriteThrough. With symbolic links to the real devices, you can test several drives in parallel. This might be helpful if you have, for example, one RAID controller with two backplanes. You could build volumes per BP, test them in parallel, and find the limits of the RAID controller.

This is the initial release on Freecode.