2009-04-24, 20:28
First of all let me clear one thing up... multithreading is working fine. The threads are spawned as normal and function fine.
The PROBLEM is that both threads seem to get scheduled to the same core on intrepid. You can see this clearly in top with thread view enabled (hit 'H'). The two decode threads spawn and each is taking ~50% core load, but if you look at core usage one core is very high and the other very low.
This seems to be alleviated, but not resolved with jaunty. I'm seeing core usage splits of ~88/55 at worst on killa, where I would regularly see 98/7 on intrepid and 75/75 on hardy. There are still quite a few dropped frames ~200, but investigation hasn't gone too deep yet.
EDIT: Clarification: Multithreading was ALWAYS working, the topic of this thread is just misleading.
The PROBLEM is that both threads seem to get scheduled to the same core on intrepid. You can see this clearly in top with thread view enabled (hit 'H'). The two decode threads spawn and each is taking ~50% core load, but if you look at core usage one core is very high and the other very low.
This seems to be alleviated, but not resolved with jaunty. I'm seeing core usage splits of ~88/55 at worst on killa, where I would regularly see 98/7 on intrepid and 75/75 on hardy. There are still quite a few dropped frames ~200, but investigation hasn't gone too deep yet.
EDIT: Clarification: Multithreading was ALWAYS working, the topic of this thread is just misleading.