Skip to content

Reduce the size of scheduler thread stacks #3496

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
Closed
brson opened this issue Sep 14, 2012 · 5 comments
Closed

Reduce the size of scheduler thread stacks #3496

brson opened this issue Sep 14, 2012 · 5 comments
Labels
A-concurrency Area: Concurrency 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. I-slow Issue: Problems and improvements with respect to performance of generated code.

Comments

@brson
Copy link
Contributor

brson commented Sep 14, 2012

They are 100KB right now, arbitrarily chosen. See how small they can be.
@nikomatsakis
Copy link
Contributor

Not critical for 0.6; removing milestone

@june0cho
Copy link
Contributor

I tested as 16KB by changing SCHED_STACK_SIZE = 1024*16 in rt/rust_sched_launcher.cpp file.
(PTHREAD_STACK_MIN was 16KB)
It works well.

@thestinger
Copy link
Contributor

Triage bump, no progress on this yet.

@pnkfelix
Copy link
Member

visiting for triage, email from 2013 sep 23. Not sure if this is still relevant in the new runtime, since we do not yet have segmented stack support there?

@thestinger
Copy link
Contributor

Support for segmented stacks has been dropped, so there's no point worrying about this anymore.

RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 23, 2024
@bors
Auto merge of rust-lang#3496 - RalfJung:thread-vector-idx, r=RalfJung
bc1538d 
global allocations: don't make up a super-high VectorIdx, just use the main thread
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-concurrency Area: Concurrency 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. I-slow Issue: Problems and improvements with respect to performance of generated code.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@brson @nikomatsakis @pnkfelix @thestinger @june0cho