skip to content
[readonly]

20 packages match "driver"

  • total 21
  • drwxr-xr-x-../
  • 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:56@ajax/cuda-driver-fake/# 0.1.0 A simulated CUDA device behind the cuda-driver table: modules, globals, streams and launches whose kernels run as C functions on CPU threads, for testing without a GPU
  • 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 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 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 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: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: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 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
  • 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 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 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: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:24@ajax/mesh-jobs-out/# 0.1.0 The job node's outputs (sends, blob pushes and fetches, persists, runs, cuts, answers, logs) and the rule that every persist is synced before the next send
  • 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 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:34@ajax/mesh-native/# 0.1.1 The native executor: programs that are executables run as worker processes on the shared mailbox, with limits, crash reports and a process per image
  • 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 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