SPIKE: ARM cell-node feasibility for warehouse-scale RAN (PTP quality, vfio/SMMU, USB-tier PinBeaconTbtt discipline)

Ouverte
#381 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Calme
Stack technique
c, docker, linux

Piste de recherche

Start with README/CLAUDE.md for the stated MediaTek USB limitation, then run the measurement plan on the Orange Pi 5 Plus: check ethtool -T and measure PTP offsets with ptp4l against the I226 baseline. Test the 8821CE/vfio path and measure PinBeaconTbtt over USB; document results, blocker scope, and candidate-board assessment. Done means a measured, costed ARM configuration fits a stated timing tier, or the evidence supports keeping x86.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement

Spike under EPIC #254. Question: can a warehouse-scale fleet of cell (gNB-DU) nodes run on ARM SBCs instead of x86 mini-PCs — cheaper, lower-power, and (the real deployment lever) PoE-powered — without giving up the timing tiers the epic depends on?

Context: the proven cell-node stack is x86 (Intel N100-class) + Intel I226 HW-PTP (~290 ns RMS vs Wi-Fi TSF) + RTL8821CE over PCIe/vfio (~12 µs submit-to-air; AP↔PTP hold ~0.67 µs via PinBeaconTbtt). devourer's ARM64 USB path is proven daily; the PCIe transport is x86-validated only. The dev rig purchase (3× J6412 boxes) proceeds regardless — this spike only decides the scale-out tier.

Three gates an ARM cell node must pass

  1. vfio/IOMMU — PcieTransport rides vfio-pci, which needs an IOMMU. Most cheap ARM SoCs wire no SMMU in front of PCIe (RK3588, i.MX8M). vfio-noiommu exists but has no DMA mapping API, so our DMA rings would need a physical-address/hugepage scheme — engineering work, not a config flag.
  2. PTP quality of the SoC MAC — "ethtool -T shows the bits" ≠ I226-grade. Needs a measured offset distribution per candidate.
  3. USB-tier fallback semantics — an ARM node driving the radio over USB is supported today, but that is the coarse-sync tier (~93 µs transport jitter). PinBeaconTbtt discipline quality over USB is unmeasured; its number decides whether warehouse cells need PCIe at all.

Measurement plan (zero-purchase: Orange Pi 5 Plus on hand answers most of it)

  • A — PTP bench on RK3588 2.5GbE: ethtool -T, then ptp4l slave against an i226 master; report offset RMS + tail vs the I226↔I226 baseline.
  • B — 8821CE in the RK3588 M.2 E-key slot: does it enumerate; does vfio (noiommu) bind; how far does pcieprobe get. Expected to stop at DMA mapping — document exactly where, and scope the noiommu DMA-ring work if it's the only blocker.
  • C — PinBeaconTbtt-over-USB discipline (any host, any generation with beacon support): close the AP↔PTP loop with the radio on USB instead of PCIe; report the hold distribution. This is the highest-value number: if it lands ~10 µs, USB-tier ARM cells are legitimate for everything except tight same-channel slot coordination.
  • D — paper pass on candidates (only if A–C are promising): RPi5/CM5 (PCIe FPC → E-key, PoE+ HAT, IOMMU status unknown), i.MX8M Plus (TSN-grade PTP, industrial), and the explicit rejects — Realtek-NIC boards (r8169 PTP patchy), MediaTek hosts (16 KB bulk-IN cap, see README/CLAUDE.md).

Exit criteria

Either: a named ARM board + attach mode (PCIe or USB) with measured PTP offset and beacon-discipline numbers fit for a stated tier of the epic (tight vs coarse), plus a costed BOM per node — or: a documented "x86 stays the cell-node platform because gate N fails and closing it costs more than the fleet savings."

Non-goal: porting PcieTransport to noiommu DMA inside this spike — scope it, don't build it.

Langage dominant
C
Étoiles
56
Forks
29
Merge moyen
3 h 43 min
PR mergées (30 j)
75

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de OpenIPC/devourer

Toutes les issues de OpenIPC/devourer

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.