From: Andi Kleen <andi@firstfloor.org>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Matthew Wilcox <willy@linux.intel.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Tracking actual disk write sources instead of flush thread
Date: Wed, 16 Apr 2014 12:33:54 -0700 [thread overview]
Message-ID: <871twxhxwd.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <534E9E9D.5030600@ubuntu.com> (Phillip Susi's message of "Wed, 16 Apr 2014 11:15:41 -0400")
Phillip Susi <psusi@ubuntu.com> writes:
>
> That seems like a severe defect. How can such a defect be tolerated
> in this day and age? Why does the io accounting not track how many
> pages the process dirties rather than how many it actually initiates
> the writeout for?
There is no per process dirty counter anyways.
The exiting proces write counter is legacy and generally useless.
If you want to track syscalls there are already plenty of ways
to do that per process. There's no way to track background
mmap flushes and it may be meaningless in this case anyways.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-04-16 19:33 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
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 [this message]
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=871twxhxwd.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=psusi@ubuntu.com \
--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.