1 |
One final thought / question / observation along the same lines... |
2 |
|
3 |
This is what got me started on this line of thinking / research... |
4 |
|
5 |
I have experimented with posix threads and find repeatedly that even a multi-threaded application yields results the same |
6 |
as if I have coded a non-multi-threaded application. |
7 |
|
8 |
If I need to give examples, I shall later, but basicly, I code with pthreads.h in C a simple counting thread which reports |
9 |
its thread number and the count. I then set main to spawn multiple threads, and in the threads, each has a random sleep in |
10 |
between printfs to show the thread / count. |
11 |
|
12 |
I even put in flushes to make sure the results weren't due to a printf buffering issue. |
13 |
|
14 |
Each and every result was of a thread counting in sequence before going to the next thread. No sleep states were put in |
15 |
the main program. It simple spawned a bunch of threads back to back, and then waited for them to "join". |
16 |
|
17 |
Is this normal? I thought even under a uniprocessor machine the threads were to time-slice like on a multicore. |