In Chrome this is base::SequencedTaskRunner which is-a base::TaskRunner. Tasks posted to a sequenced task runner are typically processed by a single thread (virtual or physical). Each such task is guaranteed to see the side-effects of the task preceding it. Sequenced task runner: A task runner which guarantees that tasks posted to it will run sequentially, in posted order.Task runner: An interface through which tasks can be posted.Tasks are executed sequentially but may hop physical threads between each one. Like a physical thread, only one task can run on a given sequence / virtual thread at any given moment and each task sees the side-effects of the preceding tasks. Sequence or Virtual thread: A chrome-managed thread of execution.There's exactly one instance per Chrome process, it serves tasks posted through base/task/thread_pool.h and as such you should rarely need to use the base::ThreadPoolInstance API directly (more on posting tasks later). In Chrome, this is base::ThreadPoolInstance. Thread pool: A pool of physical threads with a shared task queue. You should pretty much never be creating your own base::Thread's.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |