skip to content
[readonly]

14 packages match "fake"

  • total 15
  • drwxr-xr-x-../
  • 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 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 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-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: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 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 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 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/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 07:29@ajax/mesh-driver/# 0.1.1 meshd's driver thread: the only ring publisher and program-table writer; lifecycle, blinks, publishing, pipes and job items
  • 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 05:23@ajax/mesh-blobd/# 0.1.0 The blob thread's logic: this member's payloads kept durably, pushes to the copy holders with a window, fetches with failover, image assemblies, and `render`
  • 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
  • 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