Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add task pinning #6933

Closed
brson opened this issue Jun 4, 2013 · 1 comment
Closed

Add task pinning #6933

brson opened this issue Jun 4, 2013 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Jun 4, 2013

A pinned task is one that only executes on a specific scheduler. Pinned tasks contain a SchedHandle and when they are scheduled they are sent as a message to their home scheduler.

This is used for 1:1 scheduling and the platform thread.

Note that this has subtle interaction with I/O affinity, e.g. if a pinned task is doing I/O using a handle that was created on a different scheduler it may need to bounce over to the I/O scheduler temporarily.

@toddaaro
Copy link
Contributor

toddaaro commented Aug 6, 2013

Handled in a past commit. Closing.

@toddaaro toddaaro closed this as completed Aug 6, 2013
flip1995 pushed a commit to flip1995/rust that referenced this issue Mar 25, 2021
Fix bad suggestion for generics in `new_without_default` lint

Fixes bad suggestion where a type parameter was missing for `new_without_default` lint.

Fixes rust-lang#6933

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

2 participants