Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 27 Sep 2002 10:52:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 27 Sep 2002 10:52:00 -0400 Received: from 2-225.ctame701-1.telepar.net.br ([200.193.160.225]:57551 "EHLO 2-225.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Fri, 27 Sep 2002 10:51:59 -0400 Date: Fri, 27 Sep 2002 11:56:49 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: "Justin T. Gibbs" cc: Jens Axboe , Matthew Jacob , "Pedro M. Rodrigues" , Mathieu Chouquet-Stringer , , Subject: Re: Warning - running *really* short on DMA buffers while doing file transfers In-Reply-To: <389902704.1033133455@aslan.scsiguy.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 987 Lines: 27 On Fri, 27 Sep 2002, Justin T. Gibbs wrote: > writes *unless* you are creating an ISO image on your disk. In my opinion > it is much more important to optimize for the more common, concurrent > read case, than it is for the sequential write case with intermittent > reads. You're missing the point. The only reason the reads are intermittent is that the application can't proceed until the read is done and the read is being starved by writes. If the read was serviced immediately, the next read could get scheduled quickly and they wouldn't be intermittant. Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ Spamtraps of the month: september@surriel.com trac@trac.org - 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/