Posts: 48
Threads: 5
Joined: Jun 2010
Reputation:
0
Is it posible at this stage, to move the VUs to new separate threads?
I tried myself, with no luck. (Random crashes when entering 3D scenes)
Is it smt related to branches or interrupts, that makes hard to achive this?
Thanks!
Posts: 165
Threads: 2
Joined: May 2010
If you tried it this means you have some experience in development.
This thread belongs into the developer forum and is worth some real exchange with the developers.
Posts: 813
Threads: 5
Joined: Jan 2009
Reputation:
6
Probably the main problem with moving the VU's to their own thread will be synchronization overhead. You need buffers and probably spin locks I assume the times of inactivy are too quick for event triggers. And you need a bunch of logic to check that one thread is not getting too far ahead of another. You'd also be slowed down by any functional dependencies in the code and possible need to make some special admission for forwarding.
Posts: 813
Threads: 5
Joined: Jan 2009
Reputation:
6
True you probably need to lock memory access and make sure that certain things aren't changed till not needed else you might be running into a bunch of RAW, WAR , and WAW errors.
Posts: 195
Threads: 0
Joined: Feb 2009
Reputation:
5
After some experiments we concluded that running the VU in parallel with the R5900 is almost certainly not worthwhile.
Posts: 813
Threads: 5
Joined: Jan 2009
Reputation:
6
Overhead eat what little gains there are or is the R5900 not doing enough for the offload of the VU's to be any use?