Date: Fri, 27 Jun 2003 12:17:38 +0300 From: Alexey Zelkin <phantom@FreeBSD.org.ua> To: deischen@freebsd.org Cc: David Xu <davidxu@freebsd.org> Subject: Re: libkse & jdk14: signals(?) breakage Message-ID: <20030627121738.A28850@phantom.cris.net> In-Reply-To: <Pine.GSO.4.10.10306262044110.21318-100000@pcnet5.pcnet.com>; from eischen@vigrid.com on Thu, Jun 26, 2003 at 08:48:21PM -0400 References: <20030627005225.A25700@phantom.cris.net> <Pine.GSO.4.10.10306262044110.21318-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Thu, Jun 26, 2003 at 08:48:21PM -0400, Daniel Eischen wrote: > > > > > > 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. Unfortunatelly no :-( There're a lot of problems with customs in my country with receiving "free" computers and therefore I did not posted entry to wishlist. > Do you have any performance benchmarks so we can compare > against libc_r (or even libthr)? Not yet. Functional changes have more priority for me than benchmarking, sorry. libkse&libthr issues were "maybe need to be fixed" issues :-) > BTW, thanks for taking the time to run these tests :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030627121738.A28850>