Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751484AbWJRNhk (ORCPT ); Wed, 18 Oct 2006 09:37:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751485AbWJRNhk (ORCPT ); Wed, 18 Oct 2006 09:37:40 -0400 Received: from unthought.net ([212.97.129.88]:53000 "EHLO unthought.net") by vger.kernel.org with ESMTP id S1751484AbWJRNhj (ORCPT ); Wed, 18 Oct 2006 09:37:39 -0400 Date: Wed, 18 Oct 2006 15:37:41 +0200 From: Jakob Oestergaard To: Nick Piggin Cc: Jens Axboe , Alan Cox , Arjan van de Ven , "Phetteplace, Thad (GE Healthcare, consultant)" , linux-kernel@vger.kernel.org Subject: Re: Bandwidth Allocations under CFQ I/O Scheduler Message-ID: <20061018133740.GZ23492@unthought.net> Mail-Followup-To: Jakob Oestergaard , Nick Piggin , Jens Axboe , Alan Cox , Arjan van de Ven , "Phetteplace, Thad (GE Healthcare, consultant)" , linux-kernel@vger.kernel.org References: <1161048269.3245.26.camel@laptopd505.fenrus.org> <20061017132312.GD7854@kernel.dk> <20061018080030.GU23492@unthought.net> <1161164456.3128.81.camel@laptopd505.fenrus.org> <20061018113001.GV23492@unthought.net> <20061018114913.GG24452@kernel.dk> <20061018122323.GW23492@unthought.net> <1161175344.9363.30.camel@localhost.localdomain> <20061018124420.GI24452@kernel.dk> <4536245B.8070906@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4536245B.8070906@yahoo.com.au> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 951 Lines: 26 On Wed, Oct 18, 2006 at 10:55:55PM +1000, Nick Piggin wrote: ... > So you could say you want your database to consume no more than 50% > of disk and have your mp3 player get a minimum of 10%. Of course, > that doesn't say anything about what the time slices are, or what > latencies you can expect (1s out of every 10, or 100ms out of every > 1000?). > > It is still far from perfect, but at least it accounts for seeks vs > throughput reasonably well, and in a device independent manner. Yup - it makes sense. It would make very good sense (to me at least) if you can say "give me at least 100msec every 1sec", as was already suggested. That would take care of the latency problem too. -- / jakob - 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/