From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Wilcox <willy@linux.intel.com>
Subject: Re: Tracking actual disk write sources instead of flush thread
Date: Wed, 16 Apr 2014 10:01:47 -0400
Message-ID: <20140416140147.GA15429@linux.intel.com>
References: <534DE477.5080904@ubuntu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org
To: Phillip Susi <psusi@ubuntu.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mga02.intel.com ([134.134.136.20]:46803 "EHLO mga02.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1161077AbaDPOCA (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 16 Apr 2014 10:02:00 -0400
Content-Disposition: inline
In-Reply-To: <534DE477.5080904@ubuntu.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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.