Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Jan 2002 11:44:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Jan 2002 11:44:22 -0500 Received: from sun.fadata.bg ([80.72.64.67]:14605 "HELO fadata.bg") by vger.kernel.org with SMTP id ; Mon, 14 Jan 2002 11:44:04 -0500 To: Oliver.Neukum@lrz.uni-muenchen.de Cc: yodaiken@fsmlabs.com, Daniel Phillips , Arjan van de Ven , Roman Zippel , linux-kernel@vger.kernel.org Subject: Re: [2.4.17/18pre] VM and swap - it's really unusable In-Reply-To: <20020113223438.A19324@hq.fsmlabs.com> <87bsfx9led.fsf@fadata.bg> <16Q6V6-207eimC@fwd06.sul.t-online.com> From: Momchil Velikov In-Reply-To: <16Q6V6-207eimC@fwd06.sul.t-online.com> Date: 14 Jan 2002 18:32:27 +0200 Message-ID: <87d70c51wk.fsf@fadata.bg> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>> "Oliver" == Oliver Neukum <520047054719-0001@t-online.de> writes: Oliver> On Monday 14 January 2002 13:17, Momchil Velikov wrote: >> >>>>> "yodaiken" == yodaiken writes: >> yodaiken> It's not even clear how preempt is supposed to interact with >> SCHED_FIFO. >> >> How so ? The POSIX specification is not clear enough or it is not to be >> followed ? Oliver> You can have an rt task block on a lock held by a normal task that was Oliver> preempted by a rt task of lower priority. The same problem as with the Oliver> sched_idle patches. This can happen with a non-preemptible kernel too. And it has nothing to do with scheduling policy. - 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/