Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 11 Jan 2002 15:31:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 11 Jan 2002 15:31:02 -0500 Received: from zero.tech9.net ([209.61.188.187]:8719 "EHLO zero.tech9.net") by vger.kernel.org with ESMTP id ; Fri, 11 Jan 2002 15:31:00 -0500 Subject: Re: [2.4.17/18pre] VM and swap - it's really unusable From: Robert Love To: Alan Cox Cc: nigel@nrg.org, Rob Landley , Andrew Morton , linux-kernel@vger.kernel.org In-Reply-To: In-Reply-To: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.0.99+cvs.2001.12.18.08.57 (Preview Release) Date: 11 Jan 2002 15:33:22 -0500 Message-Id: <1010781207.819.27.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2002-01-11 at 07:37, Alan Cox wrote: > Its more than a spinlock cleanup at that point. To do anything useful you have > to tackle both priority inversion and some kind of at least semi-formal > validation of the code itself. At the point it comes down to validating the > code I'd much rather validate rtlinux than the entire kernel The preemptible kernel plus the spinlock cleanup could really take us far. Having locked at a lot of the long-held locks in the kernel, I am confident at least reasonable progress could be made. Beyond that, yah, we need a better locking construct. Priority inversion could be solved with a priority-inheriting mutex, which we can tackle if and when we want to go that route. Not now. I want to lay the groundwork for a better kernel. The preempt-kernel patch gives real-world improvements, it provides a smoother user desktop experience -- just look at the positive feedback. Most importantly, however, it provides a framework for superior response with our standard kernel in its standard programming model. Robert Love - 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/