linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@linux.intel.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Tracking actual disk write sources instead of flush thread
Date: Wed, 16 Apr 2014 10:01:47 -0400	[thread overview]
Message-ID: <20140416140147.GA15429@linux.intel.com> (raw)
In-Reply-To: <534DE477.5080904@ubuntu.com>

On Tue, Apr 15, 2014 at 10:01:27PM -0400, Phillip Susi wrote:
> 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?

Correct.

  reply	other threads:[~2014-04-16 14:02 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 [this message]
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=20140416140147.GA15429@linux.intel.com \
    --to=willy@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=psusi@ubuntu.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).