Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 27 Sep 2002 02:44:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 27 Sep 2002 02:44:58 -0400 Received: from beppo.feral.com ([192.67.166.79]:44815 "EHLO beppo.feral.com") by vger.kernel.org with ESMTP id ; Fri, 27 Sep 2002 02:44:56 -0400 Date: Thu, 26 Sep 2002 23:50:08 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jens Axboe cc: "Justin T. Gibbs" , "Pedro M. Rodrigues" , Mathieu Chouquet-Stringer , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Warning - running *really* short on DMA buffers while doing file transfers In-Reply-To: <20020927063616.GO5646@suse.de> Message-ID: 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: 1568 Lines: 37 > > > scsi_dma crap. That said, 253 default depth is a bit over the top, no? > > > > Why? Something like a large Hitachi 9*** storage system can take ~1000 > > tags w/o wincing. > > Yeah, I bet that most of the devices attached to aic7xxx controllers are > exactly such beasts. > > I didn't say that 253 is a silly default for _everything_, I think it's > a silly default for most users. > Well, no, I'm not sure I agree. In the expected life time of this particular set of software that gets shipped out, the next generation of 100GB or better disk drives will be attached, and they'll likely eat all of that many tags too, and usefully, considering the speed and bit density of drives. For example, the current U160 Fujitsu drives will take ~130 tags before sending back a QFULL. On the other hand, we can also find a large class of existing devices and situations where anything over 4 tags is overload too. With some perspective on this, I'd have to say that in the last 25 years I've seen more errors on the side of 'too conservative' for limits rather than the opposite. That said, the only problem with allowing such generous limits is the impact on the system, which allows you to saturate as it does. Getting that fixed is more important than saying a driver writer's choice for limits is 'over the top'. - 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/