Jv_AllocBytesChecked (Was: What is wrong with Vector?)

Jeff Sturm jeff.sturm@appnet.com
Fri Dec 22 16:28:00 GMT 2000

"Boehm, Hans" wrote:
> Thus I think we're stuck with hashing to find monitors.  But that in itself
> is cheap.  On X86, it's completely dominated by the cost of finding your own
> thread id, which you need to allow recursive monitor entry.  (Ulrich was in
> the process of changing linuxthreads to keep the thread id in a segment
> register.  Anyone know if that's making progress?)

The last time I looked at this, there were kernel changes needed to set
the FS (or was it GS?) segment register per task.  The code in
linuxthreads can be enabled once the kernel is ready... I have no idea
if 2.4 will handle this yet.

But other architectures should benefit from hash synchronization as
well.  Currently, linuxthreads for Alpha uses PAL_rduniq to determine
the thread ID, which should be significantly faster than examining stack


More information about the Java mailing list