Date: Wed, 21 May 2003 15:41:41 -0700
From: Andrew Morton <akpm@digeo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: must-fix list, v5
Message-Id: <20030521154141.2ede1e91.akpm@digeo.com>
In-Reply-To: <20030521152255.4aa32fba.akpm@digeo.com>
References: <20030521152255.4aa32fba.akpm@digeo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1099
Lines: 28

Andrew Morton <akpm@digeo.com> wrote:
>
>  o O(1) scheduler starvation, poor behaviour seems unresolved.
>  
>    Jens: "I've been running 2.5.67-mm3 on my workstation for two days, and
>    it still doesn't feel as good as 2.4.  It's not a disaster like some
>    revisisons ago, but it still has occasional CPU "stalls" where it feels
>    like a process waits for half a second of so for CPU time.  That's is very
>    noticable."
>  
>     Also see Mike Galbraith's work.
>  
>    Conclusion: the scheduler has issues, lots of people working on it.  Rick
>    Lindsley, Andrew Theurer.

Actually this part should have been deleted.

There have been a lot of sporadic CPU scheduler problem reports and a lot
of fixes, some in just the past day or two.

So apart from David MT's discoveries we shall be wiping the slate clean and
awaiting new reports.

-
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/