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

Track task ownership and visualize #6926

Closed
brson opened this issue Jun 4, 2013 · 4 comments
Closed

Track task ownership and visualize #6926

brson opened this issue Jun 4, 2013 · 4 comments
Labels
A-concurrency Area: Concurrency A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Jun 4, 2013

Task scheduling is about transferring ~Task pointers. During their lives they travel through many other data structures, including other tasks, the scheduler, shared pipes buffers, I/O callbacks. This is vital information that we should take and use for good.

It should only have a performance impact in debug mode.

@brson
Copy link
Contributor Author

brson commented Jun 4, 2013

Even better would be if the integration points needed for this were exposed to a remote debugging protocol.

@thestinger
Copy link
Contributor

Sending exchange allocations is also very relevant performance-wise due to possible false sharing of cache lines.

@flaper87
Copy link
Contributor

flaper87 commented Feb 5, 2014

triage bump.

@thestinger
Copy link
Contributor

#17325 means this is no longer relevant to the standard libraries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-concurrency Area: Concurrency A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

3 participants