From: "majun (F)" <majun258@huawei.com>
To: Philip Keogh <pkeogh@compusoftcs.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Help: FIO testing problem on arm64
Date: Mon, 2 Feb 2015 08:51:03 +0800 [thread overview]
Message-ID: <54CEC9F7.3050301@huawei.com> (raw)
In-Reply-To: <CAB6=LfOaY-STQyyB_nm4Eu8GCnhSRVcQGDu_h2o6J2at0qZd3w@mail.gmail.com>
Hi Philip:
Thanks for you replying.
Can you explain the case of "may step on itself" more detail ?
在 2015/1/30 16:48, Philip Keogh 写道:
> On Wed, Jan 28, 2015 at 5:36 PM, majun (F) <majun258@huawei.com> wrote:
>> Hi All:
>> I met a problem while testing the ramdisk peformance using fio.
>> The platform is arm64 , fio version is 2.1.10.
>>
>> The ramdisk is enabled on my platform , so there are dev/ram0 ...to dev/ram15 totall 16 ramdisk devices.
>> I tried to test these ramdisks performance uisng the script file list as below.
>>
>> #!/bin/bash
>> ...
>> fio --time_based ... --runtime=$runtime ... &
>> done
>> sleep $runtime
>> done
>> ...
>> But the test result is not ok.
>> The error log is:
>> ...
>>
>
> Have you tried sleeping for slightly longer then the runtime passed to fio?
>
> As a result of implementation details and the simple fact that sleep
> isn't exact, nor is fio's runtime, a script not allowing a sufficient
> buffer between backgrounded fio operations but intending to run
> operations sequentially may step on itself.
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2015-02-02 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 1:36 Help: FIO testing problem on arm64 majun (F)
2015-01-30 8:48 ` Philip Keogh
2015-02-02 0:51 ` majun (F) [this message]
2015-01-31 1:25 ` Kulkarni, Vasu
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=54CEC9F7.3050301@huawei.com \
--to=majun258@huawei.com \
--cc=fio@vger.kernel.org \
--cc=pkeogh@compusoftcs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox