Paul Horbal wrote:
.....
whilst solaris gives
201[8:25]tone@solaris-box ~ > python /usr/local/lib/python2.1/test/test_thread.py creating task 1 creating task 2 creating task 3 creating task 4 creating task 5 creating task 6 creating task 7 creating task 8 creating task 9 creating task 10 waiting for all tasks to complete ..etc... I just recognized that this is not necessary a problem...
There are different policies as to when a new thread gets CPU control: * give control to the new thread before the parent can continue * let the parent continue and start the new thread later Apparently, Linux uses the first and Solaris the second policy. The threads are indeed run in parallel (in coroutine fashion), as the order of task completion demonstrates. All tasks terminate in increasing execution length. Does not look bad for Solaris... Dieter