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.

Sign up for GitHub

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

Jump to bottom

Add 1:1 Scheduling Mode #595

Closed
eholk opened this issue Jun 29, 2011 · 5 comments
Closed

Add 1:1 Scheduling Mode #595

eholk opened this issue Jun 29, 2011 · 5 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@eholk
Copy link
Contributor

eholk commented Jun 29, 2011

Add a way to make each task run in its own thread.
@ghost ghost assigned eholk Jun 29, 2011
@brson
Copy link
Contributor

brson commented Dec 2, 2011

I'm planning on reintroducing the domain concept, where our current set of schedulers would be something like a 'generic' domain that just does it's best to schedule across cores. Then we would also have a thread domain, which is just a single-threaded scheduler. Then we could have a 1:1 domain where all tasks get their own thread. Possibly we could have some mechanism to pick the scheduler that main spawns into.

@brson brson mentioned this issue Feb 9, 2012
Closed
@brson
Copy link
Contributor

brson commented Mar 12, 2012

The task API surfaces this concept now, but it's still not implemented in the runtime.

@ghost ghost assigned brson Mar 15, 2012
@brson brson mentioned this issue Sep 24, 2012
Closed
@bstrie
Copy link
Contributor

bstrie commented Jun 5, 2013

@brson, is this still relevant with the upcoming scheduler?

@huonw
Copy link
Member

huonw commented Jul 30, 2013

Triage visit; echoing @bstrie's question: @brson, is this still relevant with the new scheduler?

@toddaaro
Copy link
Contributor

toddaaro commented Aug 6, 2013

Done in PR #8221

@toddaaro toddaaro closed this as completed Aug 6, 2013
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@bors
Auto merge of rust-lang#596 - Susurrus:master, r=alexcrichton
fda4049 
Use NOCANCEL variants for close on Mac

The default `close()` on OS X does not provide clear errors, instead the `$NOCANCEL` variants should be used. These are available as of OS X 10.6 onwards.

Fixes rust-lang#595.
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
@vchuravy @wsmoses
Don't free a gurantueed null-pointer (rust-lang#595)
16ed986 
* Don't free a gurantueed null-pointer

* Handle hypot

* Remove vec free

Co-authored-by: William S. Moses <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@eholk @brson @toddaaro @bstrie @huonw