Skip to content

implement ThreadPerCore #3465

New issue

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

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

Already on GitHub? # to your account

Closed
jesse99 opened this issue Sep 12, 2012 · 2 comments
Closed

implement ThreadPerCore #3465

jesse99 opened this issue Sep 12, 2012 · 2 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@jesse99
Copy link
Contributor

jesse99 commented Sep 12, 2012

This needs to be made useable by rust users. One use case is code that needs to use blocking foreign calls: often this will be done within a task using SingleThread (to avoid blocking other tasks on the thread). But that task may need to spawn sub-tasks, and those should normally be spawned using the default scheduling mode. Unfortunately trying to do so results in task failed at 'thread_per_core scheduling mode unimplemented' so users have to do something lame like using ManualThreads(4).

@eholk
Copy link
Contributor

eholk commented Sep 12, 2012

Don't we get ThreadPerCore scheduling by default?

@brson
Copy link
Contributor

brson commented Sep 12, 2012

It is the default for the default scheduler, but there is no way to get ThreadPerCore for subsequent schedulers.

@brson brson closed this as completed in 62b51d9 Sep 13, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 16, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

3 participants