skip to content
[readonly]

18 packages match "pipes"

  • total 19
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-prog-pipesrc-n/# 0.1.0 pipesrc-n, the pipe demo's source as a native mesh worker: msgs into pipehash or digests straight to a sink, with backpressure
  • 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-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 03:26@ajax/mesh-prog-pipesink/# 0.1.0 pipesink, the pipe demo's checking sink as a native mesh worker: drains digests, verifies each sha256d, histograms latency
  • 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 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 03:26@ajax/mesh-rt-ctx/# 0.1.0 What a mesh program sees (Ctx): views, peer views, input queue, pipes, request window, exchange page, counters, ids
  • drwxr-xr-x-Oct 27 03:27@ajax/mesh-worker-ctx/# 0.1.1 What a native worker's init and task see: mesh-rt's Ctx on a CPU thread (views with fault recording, peer views, the input queue, pipes, the request window, counters)
  • 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 04:12@ajax/mesh-top-ui-fleet/# 0.1.0 mesh-top's fleet tabs: Fleet (members, placement matrix, explain, decisions, lockstep groups), Jobs (table, per-member shares, results, lease choice), Pipes (inboxes and feeds), and the fleet from the snapshots alone
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-words/# 0.1.0 Word and byte access to the mailbox at mailbox offsets: the interface pipes run over
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-prog-pipehash/# 0.1.0 pipehash, the pipe demo's GPU stage: pops msgs from a CPU source, sha256d's them a lane each, pushes digests to a CPU sink, as PTX from C
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-pipe/# 0.1.0 Pipes between programs: push into a connected inbox, pop your own
  • 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 05:23@ajax/mesh-views/# 0.1.0 The fleet's view records (kind key=value -- text) as text and JSON, and their parser
  • 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:08@ajax/mesh-sched-needs/# 0.1.0 What a program needs and prefers from the fleet scheduler (backends, arch, terms, replicas, groups, reservations) and its one-token wire form
  • 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)