skip to content
[readonly]

309 packages match "mesh"

  • total 51
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-mock-meshd/# 0.1.0 A mock meshd control port for trying mesh-top without a GPU: synthetic snapshots, trace and log (a viewer fixture only)
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-mesh/# 0.1.0 mesh-top's Mesh tab: the cluster overview (a row per system, even one known only through its peers) and a panel per machine with its GPU, nodes, peers, program chips, sparkline, network, load and node grid
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-rt-wasm/# 0.1.0 The guest runtime of wasm CPU mesh programs: Ctx, View, Exchange and MESH_PROGRAM over the mesh::* imports (wasm32)
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-net/# 0.1.0 Network rates from meshd's cumulative counters on meshd's own clock (links, NICs, ports), and their human formatting
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-views/# 0.1.0 meshd's fleet, jobs and pipes views (one record a line: kind key=value .. -- text), parsed as mesh-top reads them
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top/# 0.1.0 A terminal dashboard for meshd clusters: one poller per endpoint, every tab of crates/mesh-top (mesh, programs, doom, train, infer, http, net, load, fleet, jobs, pipes, render), and --print for one frame as text
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt/# 0.1.0 The mesh device runtime: MESH_PROGRAM(init, task) makes a resident GPU kernel (mesh_main) on the node loop, or a CPU-simulated one
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-snap/# 0.1.0 mesh-top's view of a meshd snapshot: framing checks, sections, the host block (members, fleet, jobs, load, network), trace records
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-prim/# 0.1.0 mesh-rt's device primitives for the target being compiled (PTX on nvptx64, the CPU simulator elsewhere) and the f32 helpers on them
  • 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:12@ajax/mesh-top-client/# 0.1.0 mesh-top's endpoint threads: one persistent meshd control-port connection each, polling snap and running the viewer's commands, with backoff and per-command reply timeouts
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-mock/# 0.1.0 A tiny mock of meshd's control port for mesh-top's tests and demo: synthesised snapshots, trace and log, a fake catalog, and a threaded TCP server
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-view/# 0.1.0 A bounds-checked byte window of the mailbox for mesh programs, and the program fault record
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-check/# 0.1.0 Test checks for alpha-c-mesh's packages: CHECK, CHECK_U, CHECK_I, CHECK_S, then mesh_check_done()
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-mps-worker/# 0.1.1 meshd worker: one program image in its own MPS client process, which maps the mailbox, loads its cubin and launches when meshd says so
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-infer/# 0.1.0 mesh-top's Infer tab: every machine's model curve against the target samples, and the params infer's last run read
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-http/# 0.1.0 mesh-top's HTTP tab: requests the GPU served, a curl line for the bound address, the path input and the scrollable response
  • 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 04:12@ajax/mesh-top-ui-kit/# 0.1.0 What every mesh-top pane shares: the dark palette, label and value spans, the rounded panel, machine titles, Rust-exact number formats and the no-snapshot fallbacks
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-render/# 0.1.0 mesh-top's Render tab: the pathtrace image in half-block truecolor, box-filtered, tiles tinted by who rendered them, and a fleet job's image as a member assembles it
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-exec-wasm-imports/# 0.1.0 The mesh::* imports of meshd's wasm executor: a lane's windows onto the mailbox, bounds-checked as mesh-rt's View
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-doom/# 0.1.0 mesh-top's Doom tab: the raycaster's frame in half blocks with fog, the placement's shown frame and its per-column machine markers, the minimap and the player pane
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-train/# 0.1.0 mesh-top's Train tab: per machine the loss curve on a log scale, step, rate, params, peer and slowest wait, and whether the lockstep params are bitwise identical across machines
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-net/# 0.1.0 mesh-top's network panes: the Net tab (link matrix, directed links' frames by kind, every machine's interfaces), a machine panel's Network box and the overview's network cells
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-worker/# 0.1.0 The SDK of native worker programs: mesh_worker_run(init, task) maps meshd's mailbox, says ready, and runs a slot's nodes at each run until they halt
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-load/# 0.1.0 mesh-top's load panes: the Load tab (GPU share, host CPU and pressure, cores, per-program task time, share history), a machine panel's Load box and the overview's load cells
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-fleet/# 0.1.0 mesh-top's fleet tabs: Fleet (members, placement matrix, explain, decisions, lockstep groups), Jobs (table, per-member shares, results, lease choice), Pipes (inboxes and feeds), and the fleet from the snapshots alone
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-words-host/# 0.1.0 mesh_words over a host mapping of the mailbox, with C11 atomics
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui/# 0.1.0 mesh-top's frame: the tab bar, the current tab's panes, the key help and last reply, the prompt; and the flush onto a blank screen that --print and the golden frames read
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-sim-mailbox/# 0.1.0 A host mailbox with one mesh program slot and the host side of its ticket ring, request window and input queue, for testing programs on the CPU simulator
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-prog-infer/# 0.1.0 infer, the mesh program that evaluates train's cubic over a grid through a peer view, as PTX from C
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-log/# 0.1.0 meshd's log: timestamped INFO/ERROR lines on stderr through a log thread that never blocks a caller, plus the last 1000 lines in memory
  • 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 02:56@ajax/mesh-backend/# 0.1.0 The executor interface meshd's driver runs programs on: images, streams, compilers and backends (CUDA, native, wasm)
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-mps-wire/# 0.1.0 The frames between meshd and its MPS worker processes: a length, an op, its body
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-clock/# 0.1.0 Monotonic instants and durations with Rust's std::time arithmetic, and a virtual clock for tests
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-ctx/# 0.1.0 What a mesh program sees (Ctx): views, peer views, input queue, pipes, request window, exchange page, counters, ids
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-view-alloc/# 0.1.0 The view heap's first-fit page allocator (meshd gives each loaded program its view from it)
  • drwxr-xr-x-Oct 27 03:27@ajax/mesh-ptx-float-check/# 0.1.0 Refuses a mesh program PTX that breaks the cluster float mode (FTZ, correctly rounded, unfused float ops)
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi/# 0.1.0 The mesh contract in one include (every @ajax/mesh-abi-* package) and the layout checks that span them
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-linalg/# 0.1.0 Exact-mode GEMM tile and GEMV at mesh node scope: sequential sums, unfused, bit-identical on every GPU
  • 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 05:23@ajax/mesh-net-counters/# 0.1.0 meshd's live network counters: bytes and frames per peer link and kind, the control port's and the HTTP relay's
  • 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 02:56@ajax/mesh-cpuuse/# 0.1.0 What the CPU executors cost per slot: CPU time, resident bytes and lanes or processes, metered per thread
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-args/# 0.1.0 meshd's command line: every flag, its default and its refusal, as the Rust parses them
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-buf/# 0.1.0 A growable byte buffer for building strings and messages, with printf
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-block/# 0.1.0 Block collectives of a multi-warp mesh node in a fixed, bit-reproducible order (reduce, scan, broadcast), and typed shared memory
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-proc-usage/# 0.1.0 A process's CPU time (every thread, user and system) and resident bytes, from /proc
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-test-worker/# 0.1.0 The native lifecycle fixture: a mesh worker whose ops sleep, crash, allocate, fault, spin or exit on demand

-- more --