From: Phillip Susi <psusi@ubuntu.com>
To: linux-fsdevel@vger.kernel.org
Subject: Tracking actual disk write sources instead of flush thread
Date: Tue, 15 Apr 2014 22:01:27 -0400 [thread overview]
Message-ID: <534DE477.5080904@ubuntu.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
A lot of disk writes, especially when they are small individual files
being written by several different processes, are hidden behind the
flush thread. Is there no way to properly track the process actually
responsible for the IO, even when it is the flush thread that
initiates the writeout?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJTTeRzAAoJEI5FoCIzSKrw9WUH/jTozXvpeN7A0uN8KeafAhdk
agVupehoAYUDzDdYP3+JDkCmp5vgymzZydFasrPyLHmVqGsnojr/s/r6BowiQT73
Nks90Po+5wsburECDiuRz91POBbE5PTu0laK0fJWpTqeX+gZUlZBuNQlz8B2s2dr
wwtnN7tSVPc+H7TVrJz5CI/zW+rVjADXuA5GEshXg3/jfh9UnA/W5kKEVSbBvo7t
SwLH0jQ173qbTjWMu4DQIo4mAJ+JC0fYpxnmsIDZlIdNQ3JvbnwG03eyKJiDTRE1
hWklKcxSvv6MDBWcb0fhbIcLhfnQGGFq16szkQO1KmBg1/MDe7HSEncc+MooQOc=
=3C3I
-----END PGP SIGNATURE-----
next reply other threads:[~2014-04-16 2:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 2:01 Phillip Susi [this message]
2014-04-16 14:01 ` Tracking actual disk write sources instead of flush thread Matthew Wilcox
2014-04-16 15:15 ` Phillip Susi
2014-04-16 16:42 ` Andreas Dilger
2014-04-16 17:44 ` Zuckerman, Boris
2014-04-16 18:18 ` Phillip Susi
2014-04-16 18:28 ` Zuckerman, Boris
2014-04-16 19:27 ` Phillip Susi
2014-04-23 13:48 ` Matthew Wilcox
2014-04-23 19:39 ` Phillip Susi
2014-04-23 23:00 ` Theodore Ts'o
2014-04-24 1:20 ` Phillip Susi
2014-04-23 23:19 ` Andreas Dilger
2014-04-24 1:39 ` Phillip Susi
2014-04-28 3:27 ` Andi Kleen
2014-04-16 19:33 ` Andi Kleen
2014-04-24 19:33 ` Jan Kara
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=534DE477.5080904@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.