zao / pixeltoaster

Automatically exported from code.google.com/p/pixeltoaster
0 stars 1 forks source link

multi processor support with basic threading and mutexes #25

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
software rendering depends on CPU power, most architectures are going
multi-core

it would be a good idea to add some basic threading support to pixeltoaster
so this CPU power can be accessed in a portable way

there should be queries for the number of cores available, and to create a
thread with an optional affinity to a core -- there will be a restriction
that display open and update must occur on the same thread, but rendering
may occur on a different thread, provided you use synchronization.

Original issue reported on code.google.com by glenn.fi...@gmail.com on 7 Sep 2006 at 4:31

GoogleCodeExporter commented 9 years ago
Wow, that sounds great.

That will be some serious Intros running on the Quad cores :)

Original comment by martin.j...@gmail.com on 27 Jul 2007 at 7:28

GoogleCodeExporter commented 9 years ago
i totally think this is important, we'll be working on it in one of the upcoming
releases -- trick is keeping it simple and clean across win and unix

cheers

Original comment by glenn.fi...@gmail.com on 27 Jul 2007 at 8:55

GoogleCodeExporter commented 9 years ago
I do have some code for that laying around.  But you quickly get a fair bit of 
code,
even for a /simple/ library.  Not sure if this belongs in a small library like
pixeltoaster.  However, it would allow asynchronous listeners, and may even be
crucial when exposing internal buffers.  

Original comment by bram.deg...@gmail.com on 28 Jul 2007 at 6:01

GoogleCodeExporter commented 9 years ago
i think so now multi core cpu are getting itself complicated  in proccess of 
being 
small this inturn reduce speed

Original comment by jackjack...@gmail.com on 27 Jun 2008 at 7:36