From owner-freebsd-threads@FreeBSD.ORG Mon Jun 30 13:03:41 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4AAC37B401 for ; Mon, 30 Jun 2003 13:03:41 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 170CE43F85 for ; Mon, 30 Jun 2003 13:03:39 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h5UK3cAI029080; Mon, 30 Jun 2003 16:03:38 -0400 (EDT) Date: Mon, 30 Jun 2003 16:03:38 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Terry Lambert In-Reply-To: <3F0074A9.FE998647@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-threads@freebsd.org Subject: Re: rtprio and kse X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 20:03:42 -0000 On Mon, 30 Jun 2003, Terry Lambert wrote: > Daniel Eischen wrote: > > On Mon, 30 Jun 2003, Petri Helenius wrote: > > > So if I interpret this correctly, to achieve the "expected" result, > > > > What is the expected result? I expect the expected result > > to be exactly the way that libkse works. If you were to > > do the same thing in Solaris (pthreads), it would behave > > just like libkse works: it affects the LWP, not the thread, > > so any threads running in the LWP would benefit from > > the priority change. > > I'd expect the creation of a seperate KSEG, so that only the thread > that made the request gets the priority boost. Obviously you're expectations are not correct :-) Aside from breaking POSIX (a scope process thread being silently converted to a scope system thread), rtprio() is a system call and affects the kernel priority. -- Dan Eischen