skip to content
[readonly]

139 packages match "meshd"

  • 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 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 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-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 05:23@ajax/mesh-http-relay/# 0.1.0 meshd's HTTP port: request heads relayed to the GPU http program, and the routes meshd answers itself (the views, infer, render)
  • 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 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 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 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:27@ajax/mesh-prog-hashjob-wasm/# 0.1.0 hashjob: a CPU job program (job arrays) for meshd's wasm executor: per item, folded sha256d of LE8(i * K + j)
  • drwxr-xr-x-Oct 27 04:28@ajax/mesh-prog-pipesrc-wasm/# 0.1.0 pipesrc: the pipe demo's source on meshd's wasm executor, pushing msgs to pipehash or digests straight to a sink
  • drwxr-xr-x-Oct 27 04:28@ajax/mesh-prog-tick-wasm/# 0.1.0 tick for meshd's wasm executor: a pattern region of the view ticked one word a task and verified by sampling
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-spawn/# 0.1.0 posix_spawn of a worker with chosen descriptors and extra environment in its own process group, close-on-exec pipes, and exit statuses described as meshd reports them
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-exec-wasm-cache/# 0.1.0 meshd's --wasm-cache: compiled wasm modules on disk by image and engine hash, at most CACHE_CAP bytes, oldest evicted
  • 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:28@ajax/mesh-prog-pipesink-w-wasm/# 0.1.0 pipesink-w: the pipe demo's sink on meshd's wasm executor: drains digests, checks each against sha256d, histograms latency
  • 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 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 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: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 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:28@ajax/mesh-prog-pathtrace-wasm/# 0.1.0 pathtrace for meshd's wasm executor: tiles of the deterministic path tracer in the cluster float mode, bit for bit a GPU's tile
  • 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 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:27@ajax/mesh-prog-hello-wasm/# 0.1.0 hello for meshd's wasm executor: task = arg * 3 + 7, plus the wasm executor's test hooks (per-access cost, bulk reads, trap, spin, memory growth)
  • 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 04:27@ajax/mesh-prog-infer-wasm/# 0.1.0 infer for meshd's wasm executor: the trained cubic over a 64-point grid, reading train's params as a peer view, in the cluster float mode
  • drwxr-xr-x-Oct 27 04:28@ajax/mesh-prog-sha256d-wasm/# 0.1.0 sha256d for meshd's wasm executor: Bitcoin-style double SHA-256 nonce grinding as a job program, the GPU image's view, ops and request language
  • 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 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 05:23@ajax/mesh-host-block/# 0.1.0 meshd's host status block (S_* fields) under one lock, with its uptime clock and the live network counters
  • drwxr-xr-x-Oct 27 04:28@ajax/mesh-prog-train-wasm/# 0.1.0 train for meshd's wasm executor: SGD of a cubic on sin(pi x) samples, lockstep with the cluster through the exchange page, bit for bit the GPUs' (cluster float mode)
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-publish/# 0.1.0 The generic task publisher: one ticket ring per program slot, and the manifest's policy deciding what meshd publishes
  • 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 02:57@ajax/mesh-mps/# 0.1.0 meshd's CUDA backend: one context that blinks, or --isolation mps with a private MPS daemon and a pool of worker processes; nvJitLink as its compiler
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-view-heap/# 0.1.0 The view heap: whole pages meshd allocates to program views
  • drwxr-xr-x-Oct 27 02:56@ajax/mesh-cuda/# 0.1.0 meshd's CUDA: a primary or green context, eager module loading, the pinned mailbox, cubin modules, streams and resident-kernel launches
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-inproc/# 0.1.0 A GPU program driven in-process: compile, load, install a program-table slot in a mailbox of its own, launch, publish, stop and relaunch, through meshd's backend
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-control-protocol/# 0.1.0 meshd's control port and HTTP port, and the reasons a load can fail
  • 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 02:56@ajax/cuda-driver/# 0.1.0 The CUDA driver API calls meshd needs, loaded at runtime from libcuda.so.1 (no CUDA headers or toolkit to build), with an injectable table for tests
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-host-load/# 0.1.0 This machine's load (S_LOAD..): GPU share, CPU, PSI, memory, meshd, disk, thermal, cores
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-samplers/# 0.1.0 meshd's two once-a-second samplers: the load telemetry (machine and programs) and the network interfaces
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-host-members/# 0.1.0 Member records (M_*): each cluster member as this meshd sees 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 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 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: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:27@ajax/wasm-float-guard/# 0.1.0 meshd's load-time float guard for wasm CPU programs: f32 arithmetic only in exported mesh_ftz_* helpers, no threads, no relaxed SIMD, only mesh imports
  • 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

-- more --