skip to content
[readonly]

57 packages match "load"

  • total 51
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-load-text/# 0.1.0 The control port's load request: this machine's load and every program's, as key value lines
  • 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 05:24@ajax/mesh-load-share/# 0.1.0 The GPU share maths of the load sampler: node load record deltas, share, slices, gaps, and nearest-rank quantiles
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-load-proc/# 0.1.0 Parsers of the Linux /proc files the load sampler reads: stat, pressure, meminfo, loadavg, key-value files
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-load-prog/# 0.1.0 One program's load sample: GPU share from its node load records, task latencies from its trace, busy time, throughput, its CPU executor's cost
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-load-page/# 0.1.0 The load page: the host block's load regions mirrored into the mailbox
  • 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 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 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 01:45@ajax/mesh-abi-node-load/# 0.1.0 Node load records (NL_*): how much of the GPU the nodes got, measured from inside
  • 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 04:09@ajax/mesh-peer-view/# 0.1.0 A migration's view arriving in chunks from its source (bounded, sizes checked, duplicates counted once), and a member's smoothed load
  • 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-host-mload/# 0.1.0 Member load records (ML_*): each member's last load report
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-snapshot/# 0.1.0 Snapshot v3: the mailbox header, one section per loaded program, and the host block, in one frame for viewers
  • 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: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 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 02:57@ajax/mesh-mailbox/# 0.1.0 Host views of the mailbox words: acquire loads, release stores, atomic read-modify-writes, byte windows, and the pipe words over it
  • 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 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-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 04:08@ajax/mesh-sched-member/# 0.1.0 One fleet member as the scheduler sees it (capabilities, live load, link RTT, failures) and a program's measured performance on it
  • 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: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 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 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: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 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: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 02:56@ajax/nvjitlink/# 0.1.0 nvJitLink loaded at runtime: PTX to a cubin for the GPU's arch, off the blink, with no driver JIT fallback
  • 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 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 01:45@ajax/mesh-abi-view-http/# 0.1.0 programs/http's view: a GPU HTTP server's counters, load request and windows
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-host-pload/# 0.1.0 Program load records (PL_*): GPU share, latency, throughput and CPU cost per slot
  • 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 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 03:26@ajax/mesh-prog-http/# 0.1.0 http, an HTTP/1.0 GET server parsed, routed and rendered by a GPU warp over the mesh program table, as PTX from C
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-sched-tracker/# 0.1.0 The fleet scheduler's rebalancer: migrations with hysteresis, a budget and dwell, the owner policy, lockstep group re-form proposals, and moves' verdicts
  • 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 02:57@ajax/mesh-occupancy/# 0.1.0 Co-residency of resident CUDA kernels: whether every program's nodes fit on the GPU at once, and how many more do
  • drwxr-xr-x-Oct 27 01:59@ajax/pathtrace-job-scene/# 0.1.0 A pathtrace fleet job's scene: the default scene with the job's setup tasks (OP_DEFAULT, OP_SET) applied in order
  • 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
  • drwxr-xr-x-Oct 27 01:59@ajax/mesh-ftz/# 0.1.0 The cluster float mode Z: f32 arithmetic with subnormal inputs and results flushed to signed zero, as the PTX .ftz ops
  • drwxr-xr-x-Oct 27 04:27@ajax/wasm-opcodes/# 0.1.0 Every WebAssembly instruction the decoder knows: its encoding, immediates, operand signature, proposal and name
  • drwxr-xr-x-Oct 27 02:56@ajax/mesh-manifest/# 0.1.0 A program's manifest (program.toml): the struct, the parser and every validation, with the Rust's error messages
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-ptx/# 0.1.0 mesh-rt's device primitives on NVIDIA GPUs as inline PTX: special registers, sys-scope ordering, atomics, warp shuffles, the block barrier
  • 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: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: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

-- more --