Skip to content

Remove lazy initialization of scheduler threads #4392

New issue
New issue
Closed
Closed
Remove lazy initialization of scheduler threads#4392
Labels
A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone
 
0.6
@brson

Description

@brson
brson
opened on Jan 9, 2013
Contributor

Each rust_scheduler has a fixed maximum threads, but only launches them lazily. This imposes a number of locking considerations and as I am intending to make major changes to the scheduler I would rather just remove this feature.

Activity

brooksbp

brooksbp commented on Jan 19, 2013

@brooksbp
brooksbp
on Jan 19, 2013
Contributor

Would you simplify by launching max_num_threads in the rust_scheduler constructor instead of lazily in create_task?

EDIT: Reverting this #3498 ?

brson

brson commented on Jan 20, 2013

@brson
brson
on Jan 20, 2013
ContributorAuthor

@brooksbp yes, it means reverting #3498

brson

brson commented on Feb 15, 2013

@brson
brson
on Feb 15, 2013
ContributorAuthor

This isn't going to matter after all.

brson
closed this as completedon Feb 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @brooksbp@brson

        Issue actions
          Remove lazy initialization of scheduler threads · Issue #4392 · rust-lang/rust