Skip to content

Make I/O threadsafe #6843

Closed
Closed

Description

@brson

uv-based I/O is bound to a specific scheduler but tasks are not. This means that when a task goes to perform I/O it needs to check whether it is on the correct scheduler and if not, send itself as a message to the correct scheduler. Types that implement rtio traits will need to contain a SchedHandle to their home scheduler.

Activity

  1. huonw commented on Aug 5, 2013

    @huonw
    Contributor

    Triage 2013-08-05: grep seems to suggest that this (rtio-trait-implementors having a SchedHandle) isn't the case yet. (Although there has been a lot of work in the last 2 months, so the design plan may've changed.)

    Is this still an issue, @brson or @bblum?

  2. anasazi commented on Aug 21, 2013

    @anasazi
    Contributor

    I believe this has been resolved by #8631. Can we close @brson?

  3. alexcrichton commented on Oct 6, 2013

    @alexcrichton
    Member

    We now having the HomingIO trait, closing this.

  4. added a commit that references this issue on Mar 11, 2021
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 overflows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions