From: Jens Axboe <axboe@kernel.dk>
To: Georgios Koloventzos <g.koloventzos@gmail.com>, fio@vger.kernel.org
Subject: Re: diskutil output explained
Date: Mon, 02 Mar 2015 12:43:05 -0700 [thread overview]
Message-ID: <54F4BD49.9040806@kernel.dk> (raw)
In-Reply-To: <CAA6fs6=Dj+ZbCJ2vRSLBy6u+C2TdJZV1neq2PZBFfVuC7kwVWQ@mail.gmail.com>
On 02/27/2015 06:19 PM, Georgios Koloventzos wrote:
> Hello,
>
> I am running fio to test some virtual machines of mine and I am having some
> difficulties.
> So my question as it is written on the subject.
> What exactly are the output of the --debug=diskutil command?
> I have seen the code of diskutil.c but I will like a bit more
> explanatory answer.
As the option hints at, it's just debug output. Mostly deals with how it
resolves md/dm devices to the underlying devices, and so forth. So not
sure there's that much interesting there to you, unless you are trying
to debug a problem with it.
In general, fio figures out what devices to monitor, and then
continually opens the stat files and collects the appropriate
information every 250msecs.
--
Jens Axboe
prev parent reply other threads:[~2015-03-02 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 1:19 diskutil output explained Georgios Koloventzos
2015-03-02 19:43 ` 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=54F4BD49.9040806@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=g.koloventzos@gmail.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