Hi Jens, On 08/15/2010 09:03 PM, Jens Axboe wrote: > >> Of course using clock_gettime() would be more portable. The >> point of the CPU clock is speed. If you are testing IOPS into >> the ranges of millions and doing ~5 clock calls per IO, then >> portability takes a back seat to speed. >> >> But arm needs to work of course, I will commit a patch to >> fix it as soon as I can. >> > Committed such a patch, would be nice if you could test. > Either git pull or download fio-1.43-rc1 (or latest snap). > Many thanks for the patch! I had no problem compiling it on ARM, and I ran it with no problem on an example job file: [random-writers] ioengine=libaio iodepth=4 rw=randwrite bs=32k direct=0 size=64m numjobs=4 Now, you may modify the README file to mention that the ARM platform is supported too. Thanks again, Cheers, Michael. -- Michael Opdenacker, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com + 33 621 604 642 -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
