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

Thread allocation uses two memory pools #1055

Closed
hkaiser opened this issue Jan 29, 2014 · 1 comment
Closed

Thread allocation uses two memory pools #1055

hkaiser opened this issue Jan 29, 2014 · 1 comment

Comments

@hkaiser
Copy link
Member

hkaiser commented Jan 29, 2014

The current thread allocation is based on a staged memory pool system. One pool is used for the thread objects (hpx::threads::thread_data) and one is used for the stack segments. We should try to unify this into one memory recycling scheme to reduce overheads.

@ghost ghost assigned brycelelbach Jan 29, 2014
@hkaiser hkaiser mentioned this issue Jan 29, 2014
8 tasks
@brycelelbach
Copy link
Member

This has been done (albeit in a crude fashion, but it works and does not involve ripping out large chunks of the coroutines/threading code), for all schedulers except for hierarchy. I'm going to close this anyways, though; the hierarchy scheduler is very different in design from the other schedulers, and is still very experimental.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants