From: Jens Axboe <axboe@kernel.dk>
To: "Deyoung Hong (dhong)" <dhong@micron.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Bug using ramp_time shows cpu over 100%
Date: Wed, 9 Dec 2015 08:06:50 -0700 [thread overview]
Message-ID: <5668438A.8050909@kernel.dk> (raw)
In-Reply-To: <a343b7251eb54dae85f0f85e858ee19c@BOWEX36-B.micron.com>
On 12/09/2015 02:56 AM, Deyoung Hong (dhong) wrote:
> Sorry, not sure how I made that mistake (didn't even check my email response).
> I ran various fio versions (including the latest Download ZIP) and thought I checked and saw cpu way over 100%.
No worries.
> It now looks like my custom engine does not run with the latest fio code anymore.
How so? We haven't had any changes in that area, and the other IO
engines haven't needed an update for a long time. Maybe you just need to
recompile it, if structure sizes changed.
In general, I'd recommend submitting your IO engine so it can be carried
in fio proper.
--
Jens Axboe
next prev parent reply other threads:[~2015-12-09 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 21:45 Bug using ramp_time shows cpu over 100% Deyoung Hong (dhong)
2015-12-09 2:50 ` Jens Axboe
2015-12-09 9:56 ` Deyoung Hong (dhong)
2015-12-09 15:06 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 19:36 Deyoung Hong (dhong)
2015-11-30 21:45 ` Jens Axboe
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=5668438A.8050909@kernel.dk \
--to=axboe@kernel.dk \
--cc=dhong@micron.com \
--cc=fio@vger.kernel.org \
/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