Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753951Ab1DAIGE (ORCPT ); Fri, 1 Apr 2011 04:06:04 -0400 Received: from mail-ww0-f44.google.com ([74.125.82.44]:43564 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752123Ab1DAIFn (ORCPT ); Fri, 1 Apr 2011 04:05:43 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JrFxm+OOEFaixe107tz48GdWlcn7yEKzs6KvN+oua6ymx7Ce53V5MgZQhy3Ay7Dk6C qOlBPODDC8CN6vwJ63Xr32jNwr/FLkqQksGd9ovJUZbTnk3V1HGQqbknthieu2q8rAar gayF1ohuOX+X0uxHsGysVsJrbKu+2AfRK/xZw= MIME-Version: 1.0 In-Reply-To: <20110323145418.GE13315@redhat.com> References: <20110323142505.GD13315@redhat.com> <20110323145418.GE13315@redhat.com> Date: Fri, 1 Apr 2011 10:05:41 +0200 Message-ID: Subject: Re: Support for global block IO throttling? From: Juerg Haefliger To: Vivek Goyal Cc: LKML Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 862 Lines: 22 Hi Vivek, > Also current IO controller does not work for NFS. So if a global limit > is imposed in higher layers it will solve that issue too. > > Also if you implement it above page cache then it should automatically > handle the case of async writes too. The downside is that if limits > are low, buffered writers will be throttled very frequently. I'm not exactly sure where in the stack you see this global bandwidth controller. What do you mean by 'above the page cache'? I interpret this such that access to the page cache would be bandwidth limited as well? That doesn't sound right to me. Thanks ...Juerg -- 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/