From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 0122700014.0.fullrate.dk ([95.166.99.235]:55809 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756763Ab0HPW1z (ORCPT ); Mon, 16 Aug 2010 18:27:55 -0400 Message-ID: <4C69BB68.9000705@fusionio.com> Date: Mon, 16 Aug 2010 18:27:52 -0400 From: Jens Axboe MIME-Version: 1.0 Subject: Re: Build issue on arm: undefined reference to `get_cpu_clock' References: <4C6141EC.7060205@free-electrons.com> <4C6194C8.2090405@fusionio.com> <4C63B92F.3000009@free-electrons.com> <4C63DFE6.9000608@fusionio.com> <4C683A09.6090303@fusionio.com> <4C693642.3060706@free-electrons.com> In-Reply-To: <4C693642.3060706@free-electrons.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: Michael Opdenacker Cc: fio mailing list On 08/16/2010 08:59 AM, Michael Opdenacker wrote: > 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. Great, thanks for confirming. -- Jens Axboe