|
From: Hans - D. <dul...@eg...> - 2001-04-09 13:01:46
|
On Sun, 8 Apr 2001, Frank V. Castellucci wrote: > Hans Dulimarta wrote: > > > > "Frank V. Castellucci" wrote: > > > > > > Hans, > > > > > > Is libcl++ ready for a release? I haven't had a chance to try out the > > > Thread stuff, did it work the way you expected? > > > > threadTerminated handler works ok. At least for updating the > > thread state > > part. Cleaning via destroying context is not working. But, I > > What does this mean? Thread::destroyThreadContext does not work? > It does work but cannot be called from threadTerminated. > > guess since > > we are going to implement thread pool, this clean up is not > > really necessary. > > We can reuse the space and "return" it to the pool. > > We may want to talk about heap management somewhere in here, I've done > some neat things with activity escalation and generational heaps. The > work was more for garbage collection but was such a simple design that > it may be re-used in this case. What are you thoughts about the whole > Thread pool thing? For me thread pool implementation has a lower priority than the individual signal handling capability. But, if you can share your heap management code here, it'll be great. > > > > > I'm now working on the individual thread signal handling. > > > > > > > > The libcorelinux release will be 0.4.31 yes? > > > > Yes from me. > > Ok, I will assume that at anypoint in time during the week that you > don't have things partially working, that whatever is checked in works. > Of course if something didn't work before, I don't expect it will work > now :) Yes, you can assume that. -- Hans Dulimarta, Ph.D. | dul...@co... Research Associate | http://www.egr.msu.edu/~dulimart P: 517-432-7589 | http://snapsource.sourceforge.net F: 760-281-7691 | http://corelinux.sourceforge.net ECE Dept. Michigan State University, E. Lansing, MI 48824 |