Bound Threads (Re: Process vs Thread: what are the consequences?)

From:

"Kenneth P. Turvey" <kt-usenet@squeakydolphin.com>

Newsgroups:

comp.lang.java.programmer

Date:

15 Nov 2007 15:53:58 GMT

Message-ID:

<473c6b96$0$1786$ec3e2dad@news.usenetmonster.com>

On Tue, 13 Nov 2007 16:04:12 +0000, Kenneth P. Turvey wrote:

Just based on some experimentation I was doing, this doesn't seem to be
true. I'm running Linux with the Sun JVM, and it didn't map each Java
thread to a native thread until the Java thread was spending enough time
executing. I was actually trying to get this mapping (1 to 1) and found
it impossible to guarantee under Linux with the Sun JVM.

Under Solaris there is the -XX:UseBoundThreads (or something similar) to
get that behavior, but under Linux no such option exists.

I will freely admit that my experiment could have been flawed, but it
wasn't behaving as if it was using more than a single native thread. I
suspect that the article above is out of date.

I hate to followup my own post, but I've been looking at this problem
again and I'm really just unhappy with how it works. Since this can so
easily be solved under Solaris, and Lew (I think?) mentioned that this is
all JVM dependent. I was hoping somebody could point me to a JVM that
runs under Linux that supports the -XX:UseBoundThreads option or something
similar. I want a 1:1 mapping between native threads and Java threads and
I just can't seem to get it.

Does anyone have any idea? (BTW, I checked IBM's JVM).

--
Kenneth P. Turvey <kt-usenet@squeakydolphin.com>