Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 1 Oct 2002 13:32:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 1 Oct 2002 13:31:19 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:38833 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id ; Tue, 1 Oct 2002 13:30:00 -0400 Date: Tue, 1 Oct 2002 19:31:19 +0200 From: Jens Axboe To: Daniel Phillips Cc: Rik van Riel , Richard.Zidlicky@stud.informatik.uni-erlangen.de, zippel@linux-m68k.org, linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org Subject: Re: 2.4 mm trouble [possible lru race] Message-ID: <20021001173119.GY3867@suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 951 Lines: 25 On Tue, Oct 01 2002, Daniel Phillips wrote: > On Tuesday 01 October 2002 18:56, Rik van Riel wrote: > > On Tue, 1 Oct 2002, Daniel Phillips wrote: > > > On Tuesday 01 October 2002 16:20, Richard.Zidlicky@stud.informatik.uni-erlangen.de wrote: > > > > > > no preempt or anything fancy, m68k vanila 2.4.19 (well almost). > > > > > > Vanilla would be CONFIG_SMP=y, is that what you have? > > > > Somehow I doubt Linux supports m68k SMP machines ;) > > CONFIG_SMP=y works perfectly well on single cpu machines - it forces > the spinlocks to actually exist. It's not supposed to change any > behaviour, but you never know. Behaviour is obviously changing here. Again, m68k was the target. -- Jens Axboe - 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/