From: Phillip Susi <psusi@ubuntu.com>
To: "Zuckerman, Boris" <borisz@hp.com>,
Matthew Wilcox <willy@linux.intel.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Tracking actual disk write sources instead of flush thread
Date: Wed, 16 Apr 2014 15:27:52 -0400 [thread overview]
Message-ID: <534ED9B8.9090605@ubuntu.com> (raw)
In-Reply-To: <4C30833E5CDF444D84D942543DF65BDA625F5246@G4W3303.americas.hpqcorp.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 4/16/2014 2:28 PM, Zuckerman, Boris wrote:
> [bz:] In such case I'd rather have lighter implementation of
> caching layer, than ability to track disk IOs per process. IOs per
> process can be tracked by other tools...
What other tools?
I can envision blktrace being extended to hook into the mm layer to
track the real source of writes, but without any overhead when the
trace is not running.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTTtm3AAoJEI5FoCIzSKrwPPkIAJKnDv4uJfBAufqRlQbRPmcM
T3F6Dapzs2XSiMaBCaMeZQx4Zp7wxn79IM76GQeNUekHrV74kFqwLF7ezLpAviEm
IBdnhWv3uJXS6uX40os0DOqlRj5H49EhPzbLN6f5z4ARds06Zc+Z9flauCadZyce
j/1tinzm0cNYUxAIL9L+m1x7kj8Qzpq5LYyOEw7M8AL93xMGPJLgt4xWUP0JwP3l
cgiZKGD6H/ySDAFhckynCjmLdaDDNMOg8uWhyDNk8VQQnWuAzEwK3QgpfnLNSfkJ
vo1lvqMp86doRHc7pBoqY6cCU/iIrmXiMGMjVCXExkVFK4GrBHYlqlsBHnY5qys=
=mtN2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-04-16 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 2:01 Tracking actual disk write sources instead of flush thread Phillip Susi
2014-04-16 14:01 ` 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 [this message]
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=534ED9B8.9090605@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=borisz@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@linux.intel.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 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.