libkse & jdk14: signals(?) breakage

Daniel Eischen eischen at vigrid.com
Thu Jun 26 17:48:23 PDT 2003


On Fri, 27 Jun 2003, Alexey Zelkin wrote:
> hi,
> 
> On Thu, Jun 26, 2003 at 09:11:32AM +0800, David Xu wrote:
> 
> > > On Wed, Jun 25, 2003 at 09:55:21AM -0400, Daniel Eischen wrote:
> > > > On Wed, 25 Jun 2003, Alexey Zelkin wrote:
> > > > 
> > > > > hi,
> > > > > ...
> > > > > Looks like signals are still not really working in libkse.
> > > > 
> > > > David Xu is revamping signal handling (it also involves
> > > > some kernel changes).  Very alpha patches are at:
> > > > 
> > > >   http://people.freebsd.org/~davidxu/kse_sig/
> > > > 
> > > > They are not yet completely working, but might help.
> > > 
> > > Cool!  It really helped.  At least visible behaviour is same to libc_r.
> > > 
> > 
> > Your test is appreciated. I have updated the patches again,
> > they have past signal test suites included in libpthread.
> > Can you test these new patches again ?
> > http://people.freebsd.org/~davidxu/kse_sig/kern.diff
> > http://people.freebsd.org/~davidxu/kse_sig/libpthread.tgz
> 
> It just works.  Comparing to first signal patches it behaves even
> better.  I did not see any random process lockups.  Build & all TCK's
> VM tests passed.

Wow, that's great news.  Do you have an SMP system to try the
TCK tests on?  Libpthread will automatically create as many
KSEs as you have CPUs.

Do you have any performance benchmarks so we can compare
against libc_r (or even libthr)?

BTW, thanks for taking the time to run these tests :-)

-- 
Dan Eischen



More information about the freebsd-threads mailing list