From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: block device statistics question
Date: Tue, 13 May 2008 19:50:10 +0400 [thread overview]
Message-ID: <200805131950.16269.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
May I ask for clarification of block device stats meaning.
I am interested in basically two times - how long IO request has been
processed (i.e. from the very beginning it has been submitted till it was
finished) as well as how long *device* needed to process request passed to
it.
/sys/block/XXX/stat provides three set of timings:
read ticks, write ticks
io_ticks
time_in_queue
From the description in Documentation/block/stat.txt it is not exactly clear
what is counted.
read ticks, write ticks
=======================
These values count the number of milliseconds that I/O requests have
waited on this block device.
Q. Waited since which point? From the point request entered block subsystem
or from the point request has been submitted to physical device (well,
not necessarily really physical of course)
io_ticks
========
This value counts the number of milliseconds during which the device has
had I/O requests queued.
Q. "queued" - means "waited for submission"? I.e. this time does not include
actual IO processing by device? Or "queued" - submitted to device?
time_in_queue
=============
This value counts the number of milliseconds that I/O requests have waited
on this block device.
Q. What is the difference between this one and read/write ticks? It really
sounds like time_in_queue == read ticks + write ticks? In this case what is
the point in making it separate?
TIA
-andrey
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2008-05-13 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200805131950.16269.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).