Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262270AbTESQxH (ORCPT ); Mon, 19 May 2003 12:53:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262288AbTESQxH (ORCPT ); Mon, 19 May 2003 12:53:07 -0400 Received: from mx2.elte.hu ([157.181.151.9]:17123 "HELO mx2.elte.hu") by vger.kernel.org with SMTP id S262270AbTESQxG (ORCPT ); Mon, 19 May 2003 12:53:06 -0400 Date: Mon, 19 May 2003 19:02:38 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Werner Almesberger Cc: Linus Torvalds , Subject: Re: [patch] sched-cleanup-2.5.69-A0 In-Reply-To: <20030519135144.A1432@almesberger.net> Message-ID: 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: 700 Lines: 18 On Mon, 19 May 2003, Werner Almesberger wrote: > I could make it yield if anything else is runnable (I already check for > this, but just to panic). I suppose if I just set p->static_prio to > MAX_PRIO-1, this thread that would give me only very few activations > while other processes are runnable ? so you really want to run every time there's idle time, but you also want to sleep until the event that causes some other thread to run, right? Ingo - 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/