Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756537AbXLKULS (ORCPT ); Tue, 11 Dec 2007 15:11:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753459AbXLKULH (ORCPT ); Tue, 11 Dec 2007 15:11:07 -0500 Received: from phunq.net ([64.81.85.152]:56236 "EHLO moonbase.phunq.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752322AbXLKULE (ORCPT ); Tue, 11 Dec 2007 15:11:04 -0500 From: Daniel Phillips To: linux-kernel@vger.kernel.org Subject: Re: [RFC] [PATCH] A clean aEvgeniy pproach to writeout throttling Date: Tue, 11 Dec 2007 12:11:00 -0800 User-Agent: KMail/1.9.5 Cc: Andrew Morton , Peter Zijlstra References: <200712051603.02183.phillips@phunq.net> <200712111138.58197.phillips@phunq.net> <20071211200149.GA1927@kernel.dk> In-Reply-To: <20071211200149.GA1927@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712111211.00559.phillips@phunq.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 931 Lines: 19 On Tuesday 11 December 2007 12:01, Jens Axboe wrote: > On Tue, Dec 11 2007, Daniel Phillips wrote: > > The problem is solved. The main cornerstone of the solution is > > bio throttling, simply because the resources in question are > > consumed by bio transactions. > > ... because too much is pushed out. This isn't a mathematica problem, > there's more than one solution to this problem. Throttling the bio > count is one. And nobody has been able to find another. Funny that. In fact, every solution proposed so far has implicitly required the writeout traffic to be throttled, even if that throttling was not part of the patch. Without throttling, deadlock. Simple as that. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/