rtprio and kse
Daniel Eischen
eischen at vigrid.com
Mon Jun 30 15:21:57 PDT 2003
On Tue, 1 Jul 2003, David Xu wrote:
> From: "Daniel Eischen" <eischen at 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
More information about the freebsd-threads
mailing list