From e7b06322396ca837079a7b59dc601299c736fe28 Mon Sep 17 00:00:00 2001 From: Nils Andreas Svee Date: Sat, 15 Aug 2026 19:33:36 +0700 Subject: [PATCH] docs(client): correct IPDV claim in AGENTS.md The post-send sent_at change does shift the upstream IPDV component's endpoint, since ReplySample copies sent_at into client_send_mono/wall for send_ipdv_ns. Document the shift instead of claiming IPDV is unaffected. --- crates/irtt-client/AGENTS.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/crates/irtt-client/AGENTS.md b/crates/irtt-client/AGENTS.md index 9dcfa52..52779fe 100644 --- a/crates/irtt-client/AGENTS.md +++ b/crates/irtt-client/AGENTS.md @@ -153,8 +153,12 @@ send-to-reply time can exceed a second. `sent_at` remains the sole input to RTT and the downstream (`server_to_client`) one-way delay, exactly as before this capability existed; `TX_SOFTWARE` is still a software kernel timestamp near the driver -handoff, not a NIC hardware transmit time. IPDV is likewise unaffected — it -is computed from the existing userspace timestamp fields only. A normal +handoff, not a NIC hardware transmit time. `irtt-stats`'s `ReplySample` +copies public `sent_at` straight into `client_send_mono`/`client_send_wall_ns`, +which `send_ipdv_ns` compares across probes for the upstream IPDV component — +so that component shifts endpoint along with `sent_at` itself (pre-send vs. +post-send) exactly as RTT and the upstream OWD fallback do; it is not a +separate invariant. A normal reply and a measurable late reply (one whose `PendingProbe` is still retained in `TimedOutMap`) apply the identical selection policy; an untracked late reply has no retained probe and stays unmeasurable, and a