-
- Downloads
[Runtime] switch batch schedule interface from STL to C array style
Using the STL iterator based approach has caused more harm than it has advantages. First of all it is unneeded we know how the Fibers we want to schedule are stored and don't need a algorithmic generic abstraction. We keep Fibers pointers in continues memory for memory locality benefits therefore we can simply use the C dynamic array style of passing the Fibers to the scheduler. This removes the template from the batched schedule methods and allows us to use virtual functions to specialize the batched scheduleFromAnywhere method.
Showing
- emper/Runtime.cpp 1 addition, 1 deletionemper/Runtime.cpp
- emper/Runtime.hpp 4 additions, 6 deletionsemper/Runtime.hpp
- emper/Scheduler.hpp 7 additions, 10 deletionsemper/Scheduler.hpp
- emper/io/IoContext.cpp 1 addition, 1 deletionemper/io/IoContext.cpp
- emper/io/IoContext.hpp 3 additions, 4 deletionsemper/io/IoContext.hpp
- emper/lib/adt/BoostSharedMutexUnboundedQueue.hpp 7 additions, 0 deletionsemper/lib/adt/BoostSharedMutexUnboundedQueue.hpp
- emper/lib/adt/LockedSet.hpp 7 additions, 0 deletionsemper/lib/adt/LockedSet.hpp
- emper/lib/adt/MutexUnboundedQueue.hpp 7 additions, 0 deletionsemper/lib/adt/MutexUnboundedQueue.hpp
- emper/lib/adt/RwLockUnboundedQueue.hpp 8 additions, 0 deletionsemper/lib/adt/RwLockUnboundedQueue.hpp
- emper/lib/adt/SharedMutexUnboundedQueue.hpp 7 additions, 0 deletionsemper/lib/adt/SharedMutexUnboundedQueue.hpp
Loading
Please register or sign in to comment