Skip to content

Track task ownership and visualize #6926

@brson

Description

@brson
Contributor

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.

Activity

brson

brson commented on Jun 4, 2013

@brson
ContributorAuthor

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

thestinger

thestinger commented on Sep 16, 2013

@thestinger
Contributor

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

flaper87

flaper87 commented on Feb 5, 2014

@flaper87
Contributor

triage bump.

thestinger

thestinger commented on Sep 26, 2014

@thestinger
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

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-concurrencyArea: ConcurrencyA-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @flaper87@brson@thestinger

        Issue actions

          Track task ownership and visualize · Issue #6926 · rust-lang/rust