Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » what about WorkQueue : public CoWork
Re: changed CoWork and derived WorkQueue [message #24900 is a reply to message #24899] Wed, 03 February 2010 15:08 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
kohait00 wrote on Wed, 03 February 2010 09:03

hi there, here comes a changed CoWork, which now basicly is able to specify wheather to use common/static threadpool or own thread pool (is beeing decided in CoWork() based on threadnr < 0 -> common pool)

the WorkQueue then is a simple derived class, which specifies 1 for threadnr and thus uses own thread.

this is subject to test Smile.. if anyone besides me would need that.

regarding wild CoWork ctor init list:
it might be that the init order could differ, so the One<Pool> _opool could be not initialized before setting up pool.
this could be changed in a way that pool() -> pool(int threadnr = -1, CoWork * _this) returns either the global pool or costructs One<Pool>, which now is done in CoWork init list Smile

comments welcome


Why should not WorkQueue use the same static thread pool?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: DnD hangs in MT Refresh()ing
Next Topic: Linux MT problems with time functions
Goto Forum:
  


Current Time: Sat May 04 08:17:42 CEST 2024

Total time taken to generate the page: 0.02615 seconds