Nils Andreas Svee
798efaf360
Expose the negotiated schedule end only while the schedule is unfinished, and include it among Active targets' non-send deadlines. This keeps finite expiry independent of socket writability and of Burst/Staggered pacing. Staggered release gating continues to apply only to send opportunities. The existing expiry path marks the schedule finished, removing its lifetime deadline before pending probes continue draining. No new state, readiness handling, cadence, or drain/close policy is introduced. Continuous schedules have no lifetime deadline. The prior public-API Linux namespace/veth/TBF investigation observed genuine EAGAIN with Burst pacing, 500 ms duration, 1 ms interval, 1400-byte probes, and 20 ms probe timeout. Polling stopped around 327 ms after pending probes disappeared, remained stalled beyond 1.5 s, and resumed on queue release. Staggered applicability follows from the shared deadline selection; it was not separately reproduced under TBF. Retain two deterministic owning-layer tests for schedule deadline lifetime and managed selection under send_waiting and stagger gating, using ordinary Instant values and a production socket. Keep the privileged networking harness as investigation evidence rather than adding bespoke test machinery. Validation: formatting; focused schedule/managed tests; managed lifecycle, behavior, and blocking-owner integration tests; workspace all-feature check, all-target tests, doctests, and strict Clippy; client no-default-features check/tests/strict Clippy and Tokio-free normal dependency tree; Linux all-feature client and integration suites, including ancillary transport.
irtt-client
Reusable client/session library for IRTT-compatible round-trip-time probing: socket lifecycle, open negotiation, probe send/receive, loss/duplicate/late classification, and a typed event stream.
Looking for the CLI?
If you just want to run probes from the command line, use the
irtt-rs application package instead,
which installs the irtt-client binary. This crate is the library the
binaries are built on.
API tiers
Client— runtime-free blocking adapter. No Tokio dependency; this is the default build.AsyncClient(featuretokio) — low-level Tokio adapter for callers that own a runtime and drive readiness directly.managed(featuretokio) — a unified managed driver:ManagedClientTask/ManagedClientHandlefor multi-target orchestration under a Tokio runtime, andBlockingManagedClientfor synchronous callers, which owns its own dedicated current-thread runtime.
Client and AsyncClient send one probe whenever called. They expose the
negotiated parameters, pending-probe status, and timeout deadlines; callers
own cadence and run duration. The managed driver provides fixed cadence,
missed-slot handling, finite runs, and staggered or burst pacing. Low-level
EchoSent events leave scheduled_at and timer_error absent; the managed
driver supplies those schedule measurements.
Tokio stays optional: the default build has no runtime and no Tokio dependency at all.
See examples/ in the repository for runnable examples of each tier.
Documentation
Full API documentation is on docs.rs/irtt-client.
Project
Part of irtt-rs, an independent Rust implementation of an IRTT-compatible protocol stack.