All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: fio mailing list <fio@vger.kernel.org>
Subject: Re: Build issue on arm: undefined reference to `get_cpu_clock'
Date: Mon, 16 Aug 2010 18:27:52 -0400	[thread overview]
Message-ID: <4C69BB68.9000705@fusionio.com> (raw)
In-Reply-To: <4C693642.3060706@free-electrons.com>

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


      reply	other threads:[~2010-08-16 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 12:11 Build issue on arm: undefined reference to `get_cpu_clock' Michael Opdenacker
2010-08-10 18:04 ` Jens Axboe
2010-08-12  9:04   ` Michael Opdenacker
2010-08-12 11:49     ` Jens Axboe
2010-08-15 19:03       ` Jens Axboe
2010-08-16 12:59         ` Michael Opdenacker
2010-08-16 22:27           ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C69BB68.9000705@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=fio@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.