From owner-freebsd-arch Tue Nov 13 14:40:17 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id AFF2537B418; Tue, 13 Nov 2001 14:40:10 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA00143; Tue, 13 Nov 2001 14:25:13 -0800 (PST) Date: Tue, 13 Nov 2001 14:25:11 -0800 (PST) From: Julian Elischer To: Daniel Eischen Cc: John Baldwin , arch@FreeBSD.ORG Subject: Re: Thread scheduling in the kernel In-Reply-To: <3BF198E2.24EE658F@gdeb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 13 Nov 2001, Daniel Eischen wrote: > I think the UTS will only set priorities for the KSE group. It > doesn't make sense to me for the (application visible) priority > to be anywhere other than the KSE group. If the kernel needs > to temporarily play with priorities for its own purposes (inheriting > priority when holding a mutex), then each thread probably needs > an active priority which is MAX(kse->inherited, kseg->prio). MAX(thread->inherited, kseg->prio) ? > > -- > Dan Eischen > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message