From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH RFC 0/5] IO-less balance_dirty_pages() v2 (simple approach) Date: Thu, 17 Mar 2011 11:51:39 -0400 Message-ID: <20110317155139.GA16195@infradead.org> References: <1299623475-5512-1-git-send-email-jack@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kara , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Wu Fengguang , Peter Zijlstra , Andrew Morton To: Curt Wohlgemuth Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:57080 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754734Ab1CQPvm (ORCPT ); Thu, 17 Mar 2011 11:51:42 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Mar 17, 2011 at 08:46:23AM -0700, Curt Wohlgemuth wrote: > But if one of one's goals is to provide some sort of disk isolation based on > cgroup parameters, than having at most one stream of write requests > effectively neuters the IO scheduler. If you use any kind of buffered I/O you already fail in that respect. Writeback from balance_dirty_page really is just the wort case right now with more I/O supposed to be handled by the background threads. So if you want to implement isolation properly you need to track the originator of the I/O between the copy to the pagecache and actual writeback.