From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261357AbTHYMtO (ORCPT ); Mon, 25 Aug 2003 08:49:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261694AbTHYMtN (ORCPT ); Mon, 25 Aug 2003 08:49:13 -0400 Received: from main.gmane.org ([80.91.224.249]:26513 "EHLO main.gmane.org") by vger.kernel.org with ESMTP id S261357AbTHYMtK (ORCPT ); Mon, 25 Aug 2003 08:49:10 -0400 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: mru@users.sourceforge.net (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=) Subject: Re: [PATCH]O18.1int Date: Mon, 25 Aug 2003 14:49:09 +0200 Message-ID: References: <200308231555.24530.kernel@kolivas.org> <200308252137.06060.kernel@kolivas.org> <200308252228.37937.kernel@kolivas.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) Cancel-Lock: sha1:AfstS+I9q0TQxeMLqrRHWkIn2tQ= Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Con Kolivas writes: >> >> >> Vanilla test1 has the spin effect. Test2 doesn't. I haven't tried >> >> >> vanilla test3 or test4. As I've said, the O16.2-O16.3 patch >> >> >> introduced the problem. With that patch reversed, everything is >> >> >> fine. What problem does that patch fix? >> >> > >> >> > It's a generic fix for priority inversion but it induces badness in >> >> > smp, and latency in task preemption on up so it's not suitable. >> >> >> >> Now I'm confused. If that patch is bad, then why is it in O18? >> > >> > No, the 16.2 patch is bad. 16.3 backed it out. >> >> OK, but it somehow made XEmacs behave badly. > > Well it was a generic fix in 16.2 that helped XEmacs as I said. O15 > also had a generic fix (child not preempting it's parent) but that > too was covering up the real issue, but it wasnt as drastic as 16.2. Of the kernels I've tested, only test1 vanilla and O16.3 and later show the problem. Btw, is it related to the XEmacs regexp search problem, or is that a different one? -- Måns Rullgård mru@users.sf.net