Timing benchmark: SDIO vs USB (RTL8733BS vs 8733BU) — confirm/refute the transport-latency hypotheses

未關閉
#235 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
冷清
技術堆疊
c

研究方向

Start with docs/timing-accuracy.md, tests/reglat.cpp, and tests/txegress_witness.cpp; first confirm dependencies #233 and #234, then settle the SDIO access model and comparison hardware. Run the USB and SDIO measurements with the shared witness and timesync tools, including ReadTsf under RX load and TA corrections. Done means a verdict on H1–H5 and the USB/SDIO/PCIe results documented in docs/timing-accuracy.md.

由索引模型根據 Issue 內容生成。

描述

enhancement

Goal

Once the RTL8733B port lands on both buses (#233 USB, #234 SDIO), the 8733BU vs 8733BS pair gives a clean apples-vs-apples experiment: same chip, same MAC, same firmware, same PHY — only the transport differs. Run it on one host with one common witness receiver to isolate the bus as the sole variable, and confirm or refute the SDIO position we predicted this session.

This extends the USB-vs-PCIe transport-latency work already in docs/timing-accuracy.md (tests/reglat.cpp, PR #228) with the SDIO middle point.

Depends on

  • #233 — RTL8733BU USB HAL merged
  • #234 — RTL8733BS SDIO transport merged

Background (measured this session)

Transport Register op Jitter (p99−p50)
USB (8822EU) ~68 µs ~64 µs
PCIe 8821CE (MMIO) ~2.2 µs ~0.08 µs
SDIO ? (predict single-digit µs) ?

Also measured: host-pushed data-frame submit-to-air jitter ~117 µs on a quiet 5 GHz channel over USB — almost entirely the USB + MAC-pipeline (CSMA minimal), i.e. the part a faster/more-deterministic bus should reduce.

Hypotheses to confirm/refute

  • H1 — register-op latency. An SDIO CMD52/53 register round-trip is single-digit µs, sitting between USB (~68 µs) and PCIe (~2.2 µs). Measure with an SDIO reglat equivalent.
  • H2 — no bulk-IN starvation. ReadTsf() is reliable during active RX on SDIO, unlike USB (where the continuous bulk-IN flood starves the control read, forcing the timesync UE to use per-frame tsfl). Measure ReadTsf success + latency under RX load, full-duplex.
  • H3 — TA actuator tightens. The closed-loop uplink timing-advance per-correction jitter drops from ~0.5–1.2 ms (USB) toward tens of µs on SDIO (the AdjustBeaconTimingFine register sequence). Re-run timesync_ta_demo over SDIO.
  • H4 — TX-egress wall unchanged. Submit-to-air jitter for host-pushed data frames stays MAC/CSMA-bound with no TX-egress timestamp — SDIO improves the submit path but does not unlock µs-precise scheduled TX (a MAC/firmware limit, transport-independent). Measure with the txegress_witness bench.
  • H5 — clean isolation. 8733BU vs 8733BS on the same host + same witness isolates the bus as the only variable, so any delta is purely transport (not chip/firmware/PHY).

Method

  1. Port both buses (#233, #234).
  2. Build an SDIO reglat + reuse tests/txegress_witness.cpp / timesync / timesync_ta_demo.sh.
  3. Run 8733BU (USB) TX and 8733BS (SDIO) TX against a common witness receiver on the same host; collect register-op, ReadTsf-under-RX, TA-jitter, and submit-to-air numbers.
  4. Fold the resulting USB | SDIO | PCIe table into docs/timing-accuracy.md.

Open questions

  • SDIO userspace access model (per #234) determines how reglat is even run — a kernel shim over sdio_func, or in-kernel measurement. This affects what "userspace latency" means for SDIO and must be settled with #234.
  • Which host provides both a USB port and an SDIO slot for the same-host comparison (an OpenIPC SoC dev board, or a desktop SDIO reader)?

Success criteria

A confirmed-or-refuted verdict on H1–H5, with a transport-latency table (register op, ReadTsf-under-RX reliability, TA per-correction jitter, submit-to-air jitter) across USB / SDIO / PCIe — the empirical basis for the transport recommendation in the LTE/5G-parity discussion.

主要語言
C
星號
56
分支
29
平均合併
3 小時 43 分鐘
30 天內合併 PR
75

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

OpenIPC/devourer 的其他 Issue

查看 OpenIPC/devourer 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。