linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 14:18:12 -0400	[thread overview]
Message-ID: <534EC964.6080702@ubuntu.com> (raw)
In-Reply-To: <4C30833E5CDF444D84D942543DF65BDA625F51A9@G4W3303.americas.hpqcorp.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/16/2014 1:44 PM, Zuckerman, Boris wrote:
> Typically File System services do not offer semantics of 
> transactional isolation. Attempts to add that took place and were 
> rejected. Therefore, we are speaking only about some potential 
> performance penalty, right?

Not at all.  This has nothing to do with transactions; it is simply a
question of being able to identify what process is causing all of the
disk IO, like via iotop.  By counting writes in the process that
initiates the writeout of dirty pages, rather than the process that
dirties the page, it renders the write io tracking largely inaccurate
to the point of being useless at times, since often the process
dirtying the pages, even with an actual write() system call, is not
the process that initiates the writeout.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTTslkAAoJEI5FoCIzSKrwb4MH/AzwLC8GXD0huUYsU7xqEIDj
ZciTTSFMVTXa47tK8jIIbPLW3vTHyf0Dm/F1rnjn8jnJwhSqnVFfYKfUTrNQy/ze
7hJQXZ2oORZxp7jwPo3bHR1Oir0T1yXQdE5Ao7/W6wWCXY+JHEEvK1nyCPIClq+T
7TCLbkA3L0qHlGpaJMU7FkE9VaT2EI/8SKrQ05Hy2pLcksiAePnerFvxgCGIjSGU
uSXPEqamzl42eqU6pyTdTMM7yJDyIhluCH02he7y56tCX7IU5oEG6LYsDYKfsVLd
mEQeO2gCwcgKSrSQsjguPwTC5vyaomrYWvFt37jvvBWjcQwWj7A/kX6N9SBQOqY=
=4zjT
-----END PGP SIGNATURE-----

  reply	other threads:[~2014-04-16 18:18 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 [this message]
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=534EC964.6080702@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 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).