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 » Core multithread dangers
Re: Core multithread dangers [message #875 is a reply to message #874] Mon, 06 February 2006 14:24 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13980
Registered: November 2005
Ultimate Member
Yes, optimize memory. Per-object lock would add enourmous data to Pte (more that would be saved by avoiding dynamic storage).

Then, "new/delete" itself have global lock and it would be called per each Pte construction/destruction without Pte global lock, so global lock for Pte does not add too much overhead IMHO. And locked areas are extremly slow (a couple of assembly instructions), which makes me believe that concurrent access will not happen very often (it is much likely to happen during new/delete).

I have tried to implement global lock version - now there are both in Core, former version commented out. Sync uvs2.

Mirek
 
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
Next Topic: SlaveProcess should be moved from Web to Core
Goto Forum:
  


Current Time: Fri May 17 01:29:34 CEST 2024

Total time taken to generate the page: 0.02362 seconds