skip to content
[readonly]

35 packages match "state"

  • total 36
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-state-file/# 0.1.0 meshd's --state file: the loaded programs, their catalog dirs and run state, written atomically
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-group-state/# 0.1.0 A member's lockstep group state (GL_*)
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-placer/# 0.1.0 One placed program's state machine across the cluster: placement changes coordinated by the leader, state handed over, frames shown on every machine
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-app/# 0.1.0 mesh-top's viewer state: one machine per meshd endpoint with the history rates come from, tabs, focus, prompts, and every key binding
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-doc/# 0.1.0 The fleet's desired state: the programs that should run, lockstep groups and placement requests, as the Rust's text document
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-shared/# 0.1.0 meshd's shared state between its threads, and the messages they send the driver, the fleet thread and the jobs thread
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-store/# 0.1.0 A fleet member's state file, written whole, synced and renamed into place before any vote, acknowledgement or commit leaves
  • drwxr-xr-x-Oct 27 01:45@ajax/sha256-compress/# 0.1.0 One SHA-256 compression function and the initial state, freestanding C
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-place-wire/# 0.1.0 The placement peer frames: F_PLACE (a placement change), F_FRAME (a frame's state and parts), F_INPUT (input to the program's owner)
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-place-compose/# 0.1.0 A placed program's state and frame parts moved through its view, and whole frames composed from parts that arrive from several machines
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-place-spec/# 0.1.0 A program's placement regions from its manifest: the shared state, the frame number and the output split into parts
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-persist/# 0.1.0 What a fleet member keeps on disk: its term, its vote, and the accepted and committed documents, as the Rust's state file text
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-plan/# 0.1.0 What makes one member's programs match the fleet's committed document: unloads, loads, upgrades, rollbacks, migrations, run states, resets; and the first document
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-prog-table/# 0.1.0 meshd's writes to the program table: entries and pipe blocks under the PT_GEN seqlock, state changes, inbox holds, flight words, fresh slots, lookups
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-edit/# 0.1.0 Changes to the fleet's desired state as the control port asks for them (load, upgrade, rollback, place, groups, sched pin/pause/cordon) and their revert
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-programs/# 0.1.0 mesh-top's Programs tab: a program table per machine (kind, state, placement, rates, task-time quantiles, executor CPU and RSS, PTX hash), the selected program's view pane with a hexdump, the trace flame chart and the log
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-program-table/# 0.1.0 The program table (PT_*): one entry per slot, its states, policies, flags and arg modes
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-control-block/# 0.1.0 A program's control block (P_*): shutdown, run state, faults, the request window, worker words, counters
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-core/# 0.1.0 The fleet's election and commit state machine (Raft's rules with PreVote and CheckQuorum, no log; a pair has a fixed coordinator), sans-IO
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-peer-relay/# 0.1.0 The fleet thread: links, the election and commit core, changes forwarded to the leader, the leader's policies and scheduler, migrations, lockstep groups and the published fleet state
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-loop/# 0.1.0 The node loop of every mesh program's kernel: tickets from the slot's ring, completion, heartbeat, load records, shutdown
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-exec-wasm-testkit/# 0.1.0 Runs wasm guest programs through meshd's wasm executor on a test mailbox: load, launch, publish tickets, read views, unload (for tests)
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-reconcile/# 0.1.0 The fleet reconciler: makes this member's programs match the committed document (loads, upgrades, migrations with views, the lockstep group's epochs and cycles, placement)
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-jobd-text/# 0.1.0 The jobs control answers: `jobs`, `job status <id>` and `job results <id> [from] [n]`, from a member's job node
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-inferd/# 0.1.0 meshd's side of an inference request: which members serve it, the call to their gpt2 worker, the answer
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-place-mode/# 0.1.1 How a program is placed across the cluster: local, pinned to one machine, or split by an assignment of its parts (with the auto split), and each machine's role
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-jobs-sched/# 0.1.0 The jobs' lease selection over the fleet scheduler's model: members, each program's needs, measured performance, weights (F4's filter and score)
  • drwxr-xr-x-Oct 27 05:25@ajax/meshd/# 0.1.0 meshd: the host daemon of the GPU mesh: the executors, the driver, the control and HTTP ports, the samplers
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-load-host/# 0.1.0 This machine's load sample: the OS readers (CPU, PSI, memory, disk, thermal), rates between samples, the machine region and the member summary
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-views/# 0.1.0 The fleet's view records (kind key=value -- text) as text and JSON, and their parser
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-jobs-table/# 0.1.0 The job table: jobs with their done items, results, runs, failures and folds; applying ops as a join-semilattice (an item's first result wins)
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-control/# 0.1.0 meshd's control port: one request line, one reply (a line or a framed body), every request byte for byte as the Rust
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-exec-wasm/# 0.1.0 meshd's wasm executor (BACKEND_WASM): CPU programs as WebAssembly modules on lease lanes, behind the backend interface
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-driver/# 0.1.0 meshd's driver thread: the only ring publisher and program-table writer; lifecycle, blinks, publishing, pipes and job items
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-jobd/# 0.1.0 meshd's jobs thread and blob thread: the job node over the peer links, the driver and the job log; the blob store's thread and its writers; the jobs view and the host block's job fields