summaryrefslogtreecommitdiffstats
path: root/include/framework/scheduling/FIFOScheduler.h
Commit message (Collapse)AuthorAgeFilesLines
* Temporary thread affinity for reconstructionDouglas Rumbaugh2024-01-311-0/+1
|
* Adjusted recon_benchmark and properly shutdown FIFOSchedulerDouglas Rumbaugh2024-01-221-0/+1
|
* FIFOScheduler: added automake wakeupDouglas Rumbaugh2024-01-221-1/+12
| | | | | | | | | | | | Sometimes, when the max thread count is exceeded, it is possible for the scheduler to lock up. This is because the scheduler is only run when a new job is put into the queue, and so it is possible for a job to be blocked by thread limitations and be left sitting in the queue. If the main program is waiting on this job to finish before scheduling a new one, then the system deadlocks. I added a second background thread to the scheduler that wakes the scheduler up every 20us to resolve this and prevent these deadlocks.
* Initial rough-out of internal statistics trackerDouglas Rumbaugh2024-01-191-14/+14
| | | | | | Need to figure out the best way to do the detailed tracking in a concurrent manner. I was thinking just an event log, with parsing routines for extracting statistics. But that'll be pretty slow.
* Fixed various concurrency bugsDouglas Rumbaugh2023-11-091-2/+5
| | | | | | | | | | 1. The system should now cleanly shutdown when the DynamicExtension object is destroyed. Before now, this would lead to use-after-frees and/or deadlocks. 2. Improved synchronization on mutable buffer structure management to fix the issue of the framework losing track of buffers during Epoch changeovers.
* Comment and License updatesDouglas Rumbaugh2023-11-071-1/+1
|
* Scheduling: Switched over to a thread pool modelDouglas Rumbaugh2023-11-061-3/+10
|
* FIFOScheduler: fixed a few synchronization issuesDouglas B. Rumbaugh2023-10-311-8/+5
|
* General Comment + Consistency updatesDouglas Rumbaugh2023-10-301-2/+1
|
* FIFOScheduler: correctly protect m_cv with a lockDouglas Rumbaugh2023-10-301-0/+5
|
* Began moving to an explicit epoch-based systemDouglas Rumbaugh2023-10-231-0/+96
I started moving over to an explicit Epoch based system, which has necessitated a ton of changes throughout the code base. This will ultimately allow for a much cleaner set of abstractions for managing concurrency.