Date: Mon, 30 Jun 2003 00:40:08 +0200 From: "Petri Helenius" <pete@he.iki.fi> To: <deischen@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: rtprio and kse Message-ID: <005001c33e8f$6d90d6c0$44d5473e@PETEX31> References: <Pine.GSO.4.10.10306291043001.7782-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > The rtprio() call affects the KSEG in which the thread runs. > So it is the KSEG that has the realtime priority, and all > threads that run in that KSEG will be affected. This doesn't > affect other KSEGs, so if you are creating system scope > threads (each has their own KSEG and KSE), they will only > be affected if you call rtprio() from their threads. > So if I interpret this correctly, to achieve the "expected" result, one should link with -lthr, not -lkse? Expected result being priorities apply only to threads which call for it. Does -lthr have any (known) issues with spinlocks like linuxthreads has, where a thread with rtprio going into a spinlock might monopolize the CPU and the other thread never gets a quantum to actually release the lock? Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005001c33e8f$6d90d6c0$44d5473e>