i am curious. given that java virtualises stuff sufficiently, couldn't a
jvm implement a many-java-threads-to-many-kernel-threads model where it
uses a pool of kernel threads as virtual CPUs to execute java code -- plus
uses native threads in a one-to-one model when calling out to native
classes? i might be missing something, but this seems to give you the
benefits of both worlds.
(plus i think you can reduce the number of stacks in use -- so that you
don't require one native stack for each java thread... means less L2
thrashing.)
i'm also curious what functionality the kernel lacks for implementing
many-to-many threads. one thing i can see lacking is something along the
lines of sun's SIGWAITING (sent when all lwps are blocked).
Dean
On Fri, 14 Jan 2000 raybry@us.ibm.com wrote:
> http://www-4.ibm.com/software/developer/library/java2/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:12 EST