Date: Thu, 10 Apr 2003 01:58:25 -0400 (EDT) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Craig Rodrigues <rodrigc@attbi.com> Cc: freebsd-threads@freebsd.org Subject: Re: Scope system threads (was Re: PS_BLOCKED) Message-ID: <Pine.GSO.4.10.10304100146500.5845-100000@pcnet1.pcnet.com> In-Reply-To: <20030410050835.GA37060@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Apr 2003, Craig Rodrigues wrote: > On Wed, Apr 09, 2003 at 02:28:22PM -0400, Daniel Eischen wrote: > > I built it just fine without modifying anything except -lkse. > > You don't even need to change that if you just install libkse > > as libc_r.so.5, but I'd rather test out libkse in small pieces > > than to have kde blow up in my face :-). > > OK, this is good news. I put a lot of time in patching up ACE > to work on FreeBSD, and some of my work also involved submitting > patches to FreeBSD. I am glad that > > > > And it all seems to build fine. > > > Now, earlier in this e-mail thread someone mentioned that certain ACE tests > were failing. Do these tests fail now with ACE 5.3.1? Yes, and perhaps a couple new tests that were added since 5.2. > FreeBSD lacks POSIX real-time signals, which was very troublesome > when I was trying to get the ACE Proactor to work properly, because > the Proactor uses POSIX AIO + POSIX RT signals. I would really > like to see POSIX RT signals on FreeBSD. > > However, since this is a threads mailing list, I assume you > are more interested in the ACE threads tests passing with KSE. > Are there any problems there? Yes, I'm talking about tests that pass with libc_r and don't with libkse. Mostly because we get SEGVs or intentional ACE aborts(). These are most likely bugs in libkse that need to be worked out. > I am also very interested in how KSE thread priorities work, because > thread priorities are used in the TAO Real-time CORBA ORB, which is > built on top of ACE. The mutex test (lib/libpthread/test/mutex_d) passes with my version of libkse. This is a good test of thread priorities. libkse should behave in the same way as libc_r, with the exception that threads could be running in different KSEs so that could affect the order of how threads run. But this is all OK by POSIX semantics (more than one scheduling domain and/or scope system threads) and is under application control. By default, you only get one KSE/KSEG. If you want others, you use pthread_setconcurrency() and/or create scope system threads. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10304100146500.5845-100000>