From: Jens Axboe <axboe@kernel.dk>
To: "Georg Schönberger" <gschoenberger@thomas-krenn.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Print info if direct I/O is used
Date: Tue, 31 Jul 2012 20:48:35 +0200 [thread overview]
Message-ID: <50182883.7060204@kernel.dk> (raw)
In-Reply-To: <4FF456C1.9070200@thomas-krenn.com>
On 2012-07-04 16:44, Georg Schᅵnberger wrote:
> Hi Jens,
>
> it would be nice if an information is printed out if direct I/O has been
> used:
> Instead of
> --------
> /usr/local/bin/fio --rw=write --direct=1 --name=usb --filename=/dev/sdb1
> usb: (g=0): rw=write, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1
> --------
> I suggest
> --------
> /usr/local/bin/fio --rw=write --direct=1 --name=usb --filename=/dev/sdb1
> usb: (g=0): rw=write, bs=4K-4K/4K-4K, ioengine=sync, direct=1, iodepth=1
> --------
> So I can verify if the page cache has been used for a test when
> inspecting the output files.
I'll take a patch to add that :-)
--
Jens Axboe
prev parent reply other threads:[~2012-07-31 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 14:44 Print info if direct I/O is used Georg Schönberger
2012-07-31 18:48 ` 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=50182883.7060204@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=gschoenberger@thomas-krenn.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