Scope system threads (was Re: PS_BLOCKED)

[David Xu]

----- Original Message ----- 
From: "Daniel Eischen" <eischen at pcnet1.pcnet.com>
To: "David Xu" <davidxu at freebsd.org>
Cc: "Julian Elischer" <julian at elischer.org>; <freebsd-threads at freebsd.org>
Sent: Wednesday, April 09, 2003 12:26 PM
Subject: Re: Scope system threads (was Re: PS_BLOCKED)


> On Tue, 8 Apr 2003, David Xu wrote:
> 
> > Daniel,
> > 
> > These are optimizations, right?
> 
> For the most part, yes.  But I thought I'd enumerate what I'd
> like to see.
> 
> > Could we stablize the libpthread before optimizing it?
> > Is per-kse problem resolved? I don't stick to this, 
> 
> I'm working on it now.  It seems to be working, but I've got to go
> through the rest of the files to make sure we don't assume that
> thread->kse is consistent.
> 
> > and if you think it should be resolved now, I would like to
> > work on it.
> 
> There are two things that I know of that need fixing/looking at.
> One is signals which we've already talked about.  The other is
> getting the remaining ACE tests to pass.  There seems to be
> 3 or 4 that fail and I can't seem to follow the C++ code well
> enough to figure out where.  Have you ever built ACE?  I've
> got an older version that I'm using (version 5.2 I think).
> My patches to get it to compile are at:
> 
>   http://people.freebsd.org/~deischen/ace5.2_patches
> 
> If a call to sigqueue() in the source code causes a compile failure,
> just change it to kill().  Read the top-level ACE_INSTALL file;
> you have to add a couple of links before compiling.  Also, it
> wouldn't build from the top-level; I just cd'd into
> ACE_Wrappers/ace and did a gmake there, and then into
> ACE_Wrappers/tests and also gmake.
> 
> If you could debug those that would help a lot.
> 
OK, I can use C++. I did ever use ACE, I will try ACE 5.2.

> I'll get another patch set up as soon as I can.  I'd like to
> commit as soon as we get signals and the ACE bugs figured out.
> Then we can work on getting multiple KSEs and KSEGs going.
> The code is mostly there; probably needs to be reworked a bit
> (along with more debugging).
> 
> -- 
> Dan Eischen