skip to content
[readonly]

28 packages match "catalog"

  • total 29
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-catalog-toml/# 0.1.0 The lines mesh-build-programs reads from a program.toml (name, backends, # hash-also, # build-os), as the Rust build script's grep and sed
  • drwxr-xr-x-Oct 27 02:56@ajax/mesh-loader/# 0.1.0 The program catalog: names confined to --programs, reading a program's manifest and PTX, image hashes and identities
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-build-programs/# 0.1.0 Builds the mesh program catalog: each program's PTX (linked and checked in the cluster float mode), wasm image, native binary and source hash, and its variants
  • 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-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-source-hash/# 0.1.0 A native mesh program's source identity: SHA-256 of its source files as path\0content in byte order, 16 hex digits
  • drwxr-xr-x-Oct 27 07:31@ajax/mesh-fleetd/# 0.1.0 meshd's fleet member over the daemon's shared state: the fleet thread's host (status block, mailbox, catalog, driver, jobs), the reconciler's driver actions, the peer channel and link queue bridges, and the F_PERF report
  • 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 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 03:26@ajax/mesh-prog-hello/# 0.1.0 hello, the smallest mesh GPU program (task = arg * 3 + 7), as PTX from C
  • drwxr-xr-x-Oct 27 04:28@ajax/mesh-prog-sha-verify-wasm/# 0.1.0 sha-verify: re-hashes sha256d's shares on the CPU beside the GPU, reading its view through reads
  • 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 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: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 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: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: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: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 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: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 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 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 07:33@ajax/meshd/# 0.1.1 meshd: the host daemon of the GPU mesh: the executors, the driver, the control and HTTP ports, the samplers, the jobs and blob threads, and a fleet member's links, leader and reconciler
  • 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 07:31@ajax/mesh-peer-relay/# 0.1.1 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