From: Klaus Kusche <klaus.kusche@computerix.info>
To: linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Subsystem responsible for /proc/diskstats timings?
Date: Sun, 9 Sep 2018 10:03:35 +0200 [thread overview]
Message-ID: <fdbf1284-a111-f99b-30e4-4d35a35b119c@computerix.info> (raw)
Hello,
Which subsystem could be responsible for
https://bugzilla.kernel.org/show_bug.cgi?id=200857
("4.18 regression: /proc/diskstats: I/O busy time not updated correctly")?
This is for AHCI SATA disks (/dev/sda, /dev/sdb, ...),
and the busy time reported by /proc/diskstats for SSD's is still (4.18.6)
to low by at least a factor of 20 (!).
Many thanks in advance for your help!
--
Prof. Dr. Klaus Kusche
Private address: Rosenberg 41, 07546 Gera, Germany
+49 365 20413058 klaus.kusche@computerix.info https://www.computerix.info
Office address: DHGE Gera, Weg der Freundschaft 4, 07546 Gera, Germany
+49 365 4341 306 klaus.kusche@dhge.de https://www.dhge.de
next reply other threads:[~2018-09-09 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 8:03 Klaus Kusche [this message]
2018-09-13 1:26 ` Subsystem responsible for /proc/diskstats timings? Omar Sandoval
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=fdbf1284-a111-f99b-30e4-4d35a35b119c@computerix.info \
--to=klaus.kusche@computerix.info \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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