-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Re-Reading the O'Reilly book "Java Threads 2nd Edition by Scott Oaks and Henry Wong", in summary: In Windows: * Threads are timesliced * With SMP, each CPU will select a currently running thread ( page 147 ) ( Therefore, no need to do some native call just to ensure all CPUs are used... even though there is code in the book to call setConcurrency() ). In Solaris: * Two-level thread model ( LWP or system threads and user threads ) * Threads are scheduled based on Solaris LWP. Each LWP ( lightweight process / system level threads ) are known and scheduled by the OS. Each LWP will run the highest priority ( user level ) thread available. * LWPs do not perform timeslicing among the eligible threads ( just like green-threads ) * Because the number of LWPs are controlled by the Solaris thread library, you may not get the "right" number of LWPs if you have, for example, a 8 CPUs ...( page 152 ). The only way to set the number of LWPs is via a native call. I have seen and heard people complaining about why their Java program in Solaris is only using 1 or 2 CPUs, and not using all the available CPUs. I always point them out to that page on the book. In Linux: Well, I hope to hear it from you guys. ;) ... since it is not in the book that I have and I am not a kernel guru ... and how is it different between 2.2 and 2.4. Thanks, John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAju6t0cACgkQAvd5SY4qWYzFMACeKCdnH21wLxRiUOgiJ/b88ntV PL0AnRWGixy6f8S9we4gotsM9RfDaPwo =Dz0k -----END PGP SIGNATURE----- ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
