diff options
author | Carl Lerche <me@carllerche.com> | 2019-11-21 23:28:39 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-11-21 23:28:39 -0800 |
commit | 8546ff826db8dba1e39b4119ad909fb6cab2492a (patch) | |
tree | 0c1cdd36aaf9d732079a4ff7a71e5c6b138e7d42 /tokio/src/runtime/shell.rs | |
parent | 6866fe426cfab0e4da3e88c673f7bef141259bb6 (diff) |
runtime: cleanup and add config options (#1807)
* runtime: cleanup and add config options
This patch finishes the cleanup as part of the transition to Tokio 0.2.
A number of changes were made to take advantage of having all Tokio
types in a single crate. Also, fixes using Tokio types from
`spawn_blocking`.
* Many threads, one resource driver
Previously, in the threaded scheduler, a resource driver (mio::Poll /
timer combo) was created per thread. This was more or less fine, except
it required balancing across the available drivers. When using a
resource driver from **outside** of the thread pool, balancing is
tricky. The change was original done to avoid having a dedicated driver
thread.
Now, instead of creating many resource drivers, a single resource driver
is used. Each scheduler thread will attempt to "lock" the resource
driver before parking on it. If the resource driver is already locked,
the thread uses a condition variable to park. Contention should remain
low as, under load, the scheduler avoids using the drivers.
* Add configuration options to enable I/O / time
New configuration options are added to `runtime::Builder` to allow
enabling I/O and time drivers on a runtime instance basis. This is
useful when wanting to create lightweight runtime instances to execute
compute only tasks.
* Bug fixes
The condition variable parker is updated to the same algorithm used in
`std`. This is motivated by some potential deadlock cases discovered by
`loom`.
The basic scheduler is fixed to fairly schedule tasks. `push_front` was
accidentally used instead of `push_back`.
I/O, time, and spawning now work from within `spawn_blocking` closures.
* Misc cleanup
The threaded scheduler is no longer generic over `P :Park`. Instead, it
is hard coded to a specific parker. Tests, including loom tests, are
updated to use `Runtime` directly. This provides greater coverage.
The `blocking` module is moved back into `runtime` as all usage is
within `runtime` itself.
Diffstat (limited to 'tokio/src/runtime/shell.rs')
-rw-r--r-- | tokio/src/runtime/shell.rs | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/tokio/src/runtime/shell.rs b/tokio/src/runtime/shell.rs index 55278667..98d0ee6f 100644 --- a/tokio/src/runtime/shell.rs +++ b/tokio/src/runtime/shell.rs @@ -1,5 +1,6 @@ +use crate::park::Park; +use crate::runtime::enter; use crate::runtime::time; -use crate::runtime::{enter, io, Park}; use std::future::Future; use std::mem::ManuallyDrop; @@ -16,11 +17,12 @@ pub(super) struct Shell { waker: Waker, } -type Handle = <io::Driver as Park>::Unpark; +type Handle = <time::Driver as Park>::Unpark; impl Shell { pub(super) fn new(driver: time::Driver) -> Shell { - let unpark = Arc::new(driver.unpark()); + // Make sure we don't mess up types (as we do casts later) + let unpark: Arc<Handle> = Arc::new(driver.unpark()); let raw_waker = RawWaker::new( Arc::into_raw(unpark) as *const Handle as *const (), @@ -62,13 +64,13 @@ fn clone_waker(ptr: *const ()) -> RawWaker { } fn wake(ptr: *const ()) { - use crate::runtime::park::Unpark; + use crate::park::Unpark; let unpark = unsafe { Arc::from_raw(ptr as *const Handle) }; (unpark).unpark() } fn wake_by_ref(ptr: *const ()) { - use crate::runtime::park::Unpark; + use crate::park::Unpark; let unpark = ptr as *const Handle; unsafe { (*unpark).unpark() } |