forked from enlightenment/efl
renderer gets threaded). if i thread at the simplest levels (low down in for example the image scaler code - one of the most expensvie gfx routnes) on an actual dual core system - performance drops by 40%. this just doesn't work well at that level. thread creates and joins per render op are just a bad thing (tm) :) so this really needs to go in much higher up and that presents problems. :( i will need to clearly define entry and exit points to and from threaded space (and thus all the locks) - remove all nested calls (where internal code goes thru the same entry/exit points traditionally so it deadlocks itself).. anyway - this here has all that code stripepd out i played with - it is just the autofoo and build stuff so we can turn on/off thread support at will in the build. SVN revision: 26817 |
||
---|---|---|
legacy |