Ok lets say you are making a formalized CPU threaded job system and scheduler that has ordering constraints and data access constraints (eg define read/write and ordering). How would you have the user describe access and ordering? (Using c++ if it's relevant to your answer)
-
For write, just schedule the tasks one at a time. Avoid locks entirely. Mutexes are not tried and true. They are tried and found wanting. Reads can all be run in parallel.
As an additional tip, if you know your “resource” is threadsafe, support parallel writers as well so that the user can decide if they need your write protections or not.
-
-
Totally makes sense & is good stuff.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.