Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 10 Oct 2002 20:48:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 10 Oct 2002 20:48:20 -0400 Received: from e34.co.us.ibm.com ([32.97.110.132]:4338 "EHLO e34.co.us.ibm.com") by vger.kernel.org with ESMTP id ; Thu, 10 Oct 2002 20:48:18 -0400 Message-ID: <3DA62120.9070609@us.ibm.com> Date: Thu, 10 Oct 2002 17:53:52 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (compatible; MSIE5.5; Windows 98; X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Ledford CC: Linus Torvalds , Patrick Mansfield , Andrew Morton , lkml Subject: Re: Degraded I/O performance, since 2.5.41 References: <3DA61041.9080808@us.ibm.com> <20021011004227.GA27073@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1128 Lines: 27 Doug Ledford wrote: > I try to keep the drivers working > at a basic level, but until I'm done, benchmarking is pretty much a waste > of time I think) Benchmarking is integral in what we're doing right now. We need to make quick decisions about what is good or bad before the freeze. This patch makes my machine unusable for anything that isn't in the pagecache. A simple "make oldconfig" on a cold tree takes minutes to complete. My grep test got an order of magnitude worse. If we have to keep this code, can we just make the default queue HUGE for now? Will that work around it? A bunch of the AIO people use QLogic cards, which I'm sure are broken by this as well. I'm going to back this patch out for all the testing trees I do, and I suggest anyone who cares about I/O on SCSI (excluding aic7xxx) after 2.5.41 do the same. -- Dave Hansen haveblue@us.ibm.com - 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/