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

Aberta
#235 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Pouca atividade
Stack de tecnologia
c

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C
Estrelas
56
Forks
29
Merge médio
3h 43min
PRs com merge (30d)
75

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de OpenIPC/devourer

Todas as issues de OpenIPC/devourer

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.