Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 13 Jan 2002 20:16:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 13 Jan 2002 20:16:40 -0500 Received: from zero.tech9.net ([209.61.188.187]:47378 "EHLO zero.tech9.net") by vger.kernel.org with ESMTP id ; Sun, 13 Jan 2002 20:16:28 -0500 Subject: Re: [2.4.17/18pre] VM and swap - it's really unusable From: Robert Love To: Roman Zippel Cc: yodaiken@fsmlabs.com, Alan Cox , Kenneth Johansson , arjan@fenrus.demon.nl, Rob Landley , linux-kernel@vger.kernel.org In-Reply-To: <3C42293F.4962EC82@linux-m68k.org> In-Reply-To: <3C41ED4E.4D3F2D2C@linux-m68k.org> <20020113171006.A17958@hq.fsmlabs.com> <3C42293F.4962EC82@linux-m68k.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 13 Jan 2002 20:19:21 -0500 Message-Id: <1010971163.1528.32.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2002-01-13 at 19:41, Roman Zippel wrote: > > That is exactly what Andrew Morton disputes. So why do you think he is > > wrong? Victor is saying that Andrew contends the hard parts of his low-latency patch are just as hard to maintain with a preemptive kernel. This is true, for the places where spinlocks are held anyway, but it assumes we continue to treat lock breaking and explicit scheduling as our only solution. It isn't under a preemptible kernel. 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/