Date: Mon, 30 Jun 2003 18:21:55 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: David Xu <davidxu@viatech.com.cn> Cc: freebsd-threads@freebsd.org Subject: Re: rtprio and kse Message-ID: <Pine.GSO.4.10.10306301817580.20764-100000@pcnet5.pcnet.com> In-Reply-To: <002501c33f55$1ed32530$0701a8c0@tiger>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Jul 2003, David Xu wrote: > From: "Daniel Eischen" <eischen@vigrid.com> > > > > 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. It is legitimate to want a single (or set) of threads to have real-time priority and not the others. Since the priority is in the KSEG, this is possible to do without fork()ing. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10306301817580.20764-100000>