Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 18 Aug 2002 14:27:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 18 Aug 2002 14:27:31 -0400 Received: from mail11.speakeasy.net ([216.254.0.211]:60867 "EHLO mail.speakeasy.net") by vger.kernel.org with ESMTP id ; Sun, 18 Aug 2002 14:27:29 -0400 Subject: Re: cerberus errors on 2.4.19 (ide dma related) From: Ed Sweetman To: Andre Hedrick Cc: linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 18 Aug 2002 14:31:30 -0400 Message-Id: <1029695490.1357.8.camel@psuedomode> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 950 Lines: 28 Preempt doesn't seem to be the culprit. Reran the test without using preempt and I got MEMORY errors within 22 seconds at udma2. So preempt is not the problem here. On Sun, 2002-08-18 at 05:19, Andre Hedrick wrote: > > 2.4.19-preempt > > All bets are off because who knows what preempt is doing to the state > machines and in PIO you are dead. > > You can not delay transaction of data between interrupts w/o having the > transport help out. But the preempt don't get it. > > If you push your request size down to 8k or to a page you preempt problems > will go away, only because granularity of requests. And the price is > performance goes in the tank. But this is preempt so who cares. - 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/