summaryrefslogtreecommitdiff
path: root/src/mbgl/actor
Commit message (Collapse)AuthorAgeFilesLines
* [core] Fix performance-unnecessary-value-param errorsThiago Marcos P. Santos2020-03-231-2/+2
| | | | As reported by clang-tidy-8.
* [core] Use weak scheduler inside mailboxAlexander Shalamov2020-01-231-14/+16
| | | | | There is no guarantee that scheduler is alive when message is pushed to the mailbox.
* [core] Introduce Pass<> class and use it for SchedulerMikhail Pozdnyakov2019-12-021-4/+4
| | | | Thus we enforce client to retain the returned `Scheduler` objects.
* [core] Introduce Scheduler::GetSequenced() APIMikhail Pozdnyakov2019-11-281-0/+27
| | | | | | The newly introduced `Scheduler::GetSequenced()` returns sequenced schedulers from the cache limited to 10 instances, preventing from spawning too many threads.
* [core] Introduce Scheduler::bindOnce() and use it in ImageManagerMikhail Pozdnyakov2019-10-101-1/+8
|
* [core] Introduce SequencedScheduler and ParallelSchedulerMikhail Pozdnyakov2019-10-071-1/+1
| | | | | | | | | | | This commit refactors `utils::ThreadPool` into a template `ThreadedScheduler` class and provides aux type aliases. So that it is possible to obtain a sequenced schedule,where all the scheduled tasks are guarantied to be executed consequently. The sequenced lightweight scheduler is required by both the orchestration thread and the refactored `FileSource` implementation.
* [core] Decouple Scheduler interface from actor modelMikhail Pozdnyakov2019-10-041-3/+9
| | | | So that it is possible to schedule normal `std::function` and use `mapbox::base::WeakPtr`.
* [core] Make the BackgroundScheduler a singletonThiago Marcos P. Santos2019-05-101-1/+19
| | | | | | | | | | - Do not carry it over everywhere as parameter, it is a shared instance anyway and the lifecycle is pretty much the app lifecycle from the moment we instantiate a map. - Rename to BackgroundScheduler because it is a Scheduler that will do tasks in the background, we don't make assumptions if it is a thread pool or a single thread. - Most importantly, remove the dependency from `core` on `platform`.
* [core] clang-tidy fixesKonstantin Käfer2019-04-051-2/+1
|
* [core] Avoid blocking in Thread<Object> constructor (#12151)Anand Thakker2018-07-031-4/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Introduce AspiringActor, EstablishedActor This pair of objects represents the two-phase (parent-thread / child-thread) construction that's needed to support constructing Thread<Object> without blocking until the child thread is up and running. An `AspiringActor<O>` is responsible for: - ownership of the actor's `Mailbox` - allocating the memory for (but *not* constructing) the target object `O` Using these two pieces--the mailbox and a stable address for `O`--an `AspiringActor<O>` can accept messages for the target object, or provide `ActorRef<O>`s that do so, before the object has actually been constructed by the corresponding `EstablishedActor<O>`. (Such messages are queued in the mailbox until after the object is constructed.) This allows for an `AspiringActor<O>` to be created and safely used by a thread other than the one on which the target object will (eventually) live. An `EstablishedActor<O>` is responsible for managing the lifetime of the target object `O` and the open/closed state of the parent's `mailbox`. The `O` object's lifetime is contained by that of its owning `EstablishedActor<O>`: the `EstablishedActor` constructor executes the `O` constructor via "placement new", constructing it at the address provided by the parent `AspiringActor`, and the `~EstablishedActor` destructor similarly executes the `~O` destructor (after closing the mailbox). `EstablishedActor` should therefore live entirely on the thread intended to own `O`. * Remove Actor#{invoke,ask}
* [core] current schedulerIvo van Dongen2017-08-091-0/+19
| | | | - Adds a way to set the current scheduler on the thread to be used whenever a mailbox is created that needs to reply on this thread
* [core] Make the mbgl/actor headers publicThiago Marcos P. Santos2017-06-263-168/+0
| | | | | They will be needed by the DefaultFileSource, something that we also export as public.
* [core] allow self closing mailbox/actorIvo van Dongen2017-05-271-2/+3
|
* [core] Block in Mailbox::close() until neither receive nor push are in progressJohn Firebaugh2017-05-241-9/+18
| | | | | | | | | | | | | | Otherwise, an ActorRef that's in the process of sending a message could attempt to access an invalid Scheduler reference: Thread 1 Thread 2 -------------------------------------------------- Scheduler::Scheduler Actor::Actor weakMailbox.lock() Actor::~Actor Scheduler::~Scheduler mailbox->push() scheduler.schedule() 💣
* [core] Move actor/{mailbox,scheduler}.hpp to public include directoryJohn Firebaugh2017-03-282-71/+0
| | | | Map constructor takes Scheduler&, and consumers are expected to define an implementation. Therefore the interface must be public.
* [core] extract weak_ptr mailbox->receive into Mailbox::maybeReceiveMike Morris2016-10-202-0/+8
|
* [core] [node] pass thread pool impl to Map constructorMike Morris2016-10-202-82/+0
| | | | | | | Updates mbgl::Map constructor usage everywhere Adds NodeThreadPool implementation using AsyncQueue to call Nan::AsyncQueueWorker from main thread
* [core] Fix ThreadPool race condition (#6388)John Firebaugh2016-09-202-7/+13
|
* [core] Document the ActorRef<O> argument passed to O's constructorJohn Firebaugh2016-09-161-6/+7
|
* [core] Use an actor model for tile worker concurrencyJohn Firebaugh2016-09-168-0/+367
View Lorry Controller Status