microsoft / microsoft/openvmm

mesh: remove global timeout thread

Open
#38 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
1.9k
Forks
238
Avg merge
1d 15h
Merged PRs (30d)
100

Description

For convenience, mesh cancel contexts are timed out via a global timeout thread. Find a better way to manage this, e.g.:

  • Pass a pal_async driver to until_cancelled. This isn't great because we want to avoid a pal_async dependency in the public API.
  • Require the platform to be initialized with an explicit driver for handling timeouts. This works OK but means every program using mesh has to remember to do this in main.
  • Grab the driver from the current task. This seems easy to screw up since we're not always running on a task.

None of these solutions is obviously the right one. But it's awkward to have this extra thread.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing mesh cancel contexts through until_cancelled and the global timeout thread. Compare the listed options: passing a pal_async driver, requiring explicit platform initialization, or obtaining the driver from the current task. Done means selecting and implementing a timeout design that removes the extra thread without adding an undesirable public API dependency.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.