From owner-freebsd-threads@FreeBSD.ORG Mon Jun 30 15:12:23 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 4DB8A37B401; Mon, 30 Jun 2003 15:12:23 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 990CD43FF3; Mon, 30 Jun 2003 15:12:20 -0700 (PDT) (envelope-from davidxu@freebsd.org) Received: from tiger (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with SMTP id h5UMCGUp011408; Mon, 30 Jun 2003 15:12:18 -0700 (PDT) (envelope-from davidxu@freebsd.org) Message-ID: <002501c33f55$1ed32530$0701a8c0@tiger> From: "David Xu" To: , "Terry Lambert" References: Date: Tue, 1 Jul 2003 06:15:28 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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: David Xu List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 22:12:23 -0000 ----- Original Message -----=20 From: "Daniel Eischen" To: "Terry Lambert" Cc: Sent: Tuesday, July 01, 2003 4:03 AM Subject: Re: rtprio and kse > 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, > > >=20 > > > 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. > >=20 > > I'd expect the creation of a seperate KSEG, so that only the thread > > that made the request gets the priority boost. >=20 > 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. > rtprio means he want to exclusively use CPU, not only between threads in process but also between threads in system, I can not image a guy is stilling using PTHREAD_SCOPE_PROCESS but not PTHREAD_SCOPE_SYSTEM to define a competition scope in process but not system wide, if he want to be rtprio in a process but not system scope, I think he'd use pthread_setprio(), otherwise setting thread to PTHREAD_SCOPE_SYSTEM is necessary. > --=20 > Dan Eischen >=20 > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to = "freebsd-threads-unsubscribe@freebsd.org" >