From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: 2.5.70-mm9 From: Mingming Cao In-Reply-To: <20030614010139.2f0f1348.akpm@digeo.com> References: <20030613013337.1a6789d9.akpm@digeo.com> <3EEAD41B.2090709@us.ibm.com> <20030614010139.2f0f1348.akpm@digeo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: 14 Jun 2003 17:41:29 -0700 Message-Id: <1055637690.1396.15.camel@w-ming2.beaverton.ibm.com> Mime-Version: 1.0 Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On Sat, 2003-06-14 at 01:01, Andrew Morton wrote: > Was elevator=deadline observed to fail in earlier kernels? If not then it > may be an anticipatory scheduler bug. It certainly had all the appearances > of that. Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5. > So once you're really sure that elevator=deadline isn't going to fail, > could you please test elevator=as? > Ok, the deadline test was run for 10 hours then I stopped it (for the elevator=as test). But the test on elevator=as (2.5.70-mm9 kernel) still failed, same problem. Some fsx tests are sleeping on io_schedule(). Next I think I will re-run test on elevator=deadline for 24 hours, to make sure the problem is really gone there. After that maybe try a different Qlogic Driver, currently I am using the driver from Qlogic company(QLA2XXX V8). Thanks, Mingming -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org