Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264201AbTGGRvM (ORCPT ); Mon, 7 Jul 2003 13:51:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264203AbTGGRvM (ORCPT ); Mon, 7 Jul 2003 13:51:12 -0400 Received: from x35.xmailserver.org ([208.129.208.51]:8094 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S264201AbTGGRvL (ORCPT ); Mon, 7 Jul 2003 13:51:11 -0400 X-AuthUser: davidel@xmailserver.org Date: Mon, 7 Jul 2003 10:58:06 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mcafeelabs.com To: Daniel Phillips cc: Mel Gorman , Jamie Lokier , Andrew Morton , Linux Kernel Mailing List , Linux Memory Management List Subject: Re: 2.5.74-mm1 In-Reply-To: <200307071728.08753.phillips@arcor.de> Message-ID: References: <20030703023714.55d13934.akpm@osdl.org> <200307071728.08753.phillips@arcor.de> 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 Content-Length: 1061 Lines: 26 On Mon, 7 Jul 2003, Daniel Phillips wrote: > That's not correct in this case, because the sound servicing routine is > realtime, which makes it special. Furthermore, Zinf is already trying to > provide the kernel with the hint it needs via PThreads SetPriority but > because Linux has brain damage - both in the kernel and user space imho - the > hint isn't accomplishing what it's supposed to. > > As I said earlier: trying to detect automagically which threads are realtime > and which aren't is stupid. Such policy decisions don't belong in the > kernel. Having hacked a little bit with vsound I can say that many sound players do not use at 100% the buffering the sound card/kernel is able to provide and they still use 4-8Kb feeding chunks. That require very short timings to not lose the time. - Davide - 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/