Date: Tue, 3 Jun 2003 05:48:15 -0400 (EDT) From: Daniel Eischen <eischen@pcnet.com> To: Tom Samplonius <tom@sdf.com> Cc: freebsd-threads@freebsd.org Subject: Re: Fwd: Re: Native JDK with libthr/libkse Message-ID: <Pine.GSO.4.10.10306030541340.12693-100000@pcnet5.pcnet.com> In-Reply-To: <Pine.BSF.4.05.10306022015260.24448-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2 Jun 2003, Tom Samplonius wrote: > > On Mon, 2 Jun 2003, Daniel Eischen wrote: > > > On Mon, 2 Jun 2003, Tom Samplonius wrote: > > > ... > > > > And I encourage the java developers to let us threads guys know > > > > what they're having problems with. It has been stated that > > > > jdk is not guaranteed to work with anything but libc_r, so > > > > contact us over at threads@. We want to see a fast and stable > > > > jdk as much as anyone else does. > > > > > > > > -- > > > > Dan Eischen > > > > > > > > > But the last that I've seen on the threads@ list is that libkse's signal > > > handling is not finished, and both libthr and libkse have incomplete SMP > > > support. I've been waiting to hear whether one of these has reached a > > > "finished" state, in order that a test build of jdk on FreeBSD 5 is not a > > > total waste... > > > > SMP libkse support should be complete. We are working on signal > > handling now, but it's fudged to mostly work. Mozilla, KDE, > > and openoffice all run with libkse. > > Does "fudged" mean that the issue MySQL not exiting has also been > resolved? That seems like something that would break a java application > real fast. I believe mysql relies on SIGHUP or a fork to handle signals. Mysql may actually work now, but I haven't tried it. I don't think the JDK relies on signals other than synchronous signals which should work OK with libkse. I was more interested in the statement that "jdk is only guaranteed to work with libc_r" that one of the Java developers posted. I took it to mean that the implementation of our jdk is geared towards libc_r (perhaps knowing internal stuff about how libc_r works). I don't want anything like that to stop us, and we can add some common APIs to the threads libraries if needed to support it. > Also at what point was support completed? I'm not sure if I need to > cvsup again. I last cvsupped -current on May 31st. Would that be the > latest and greatest libkse? That should be good. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10306030541340.12693-100000>