Date: Mon, 30 Jun 2003 11:22:03 +0200 From: "Petri Helenius" <pete@he.iki.fi> To: "Julian Elischer" <julian@elischer.org>, "Jeff Roberson" <jroberson@chesapeake.net> Cc: freebsd-threads@freebsd.org Subject: Re: rtprio and kse Message-ID: <019601c33f13$015daa30$44d5473e@PETEX31> References: <Pine.BSF.4.21.0306292332230.42233-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Theoretically any process with rt priority can monopolise the CPU if it > spins, regardless of whether it's threaded or not.. > > Is not that what having RT-priority means? Yes, but in non-threaded environment with multiple processes competing for CPU libc is not expected to have locks. In threaded environment it does have them around things like malloc. My concern is the realtime thread spinlocking waiting for a lock which is held somewhere which does not get scheduled. These locks are not visible to the appliation and thus one must either put additional mutexes around them or know that libc stuff is rtprio-thread-safe. Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?019601c33f13$015daa30$44d5473e>