Metraipolis › archive › dc_f78e7cf19dfe
From ASIC to Fleet: Lessons from Building and Operating a Hyperscaler NIC — arXiv:2610.07644
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2610.07644
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-07T11:25:44.426Z
- SHA-256 of the archived text
98d2d32a6e9ec14999b7f7f93a509817a49b033a4b7b28f9d05e7da80a0c7312- Stable URL of this page
https://metraipolis.com/documento/dc_f78e7cf19dfe
How to cite
From ASIC to Fleet: Lessons from Building and Operating a Hyperscaler NIC — arXiv:2610.07644 — arXiv (en), https://arxiv.org/abs/2610.07644 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_f78e7cf19dfe (Metraipolis archive dc_f78e7cf19dfe, sha256 98d2d32a6e9ec14999b7f7f93a509817a49b033a4b7b28f9d05e7da80a0c7312)
BibTeX
@misc{dcf78e7cf19dfe,
title = {From ASIC to Fleet: Lessons from Building and Operating a Hyperscaler NIC — arXiv:2610.07644},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2610.07644},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_f78e7cf19dfe; sha256 98d2d32a6e9ec14999b7f7f93a509817a49b033a4b7b28f9d05e7da80a0c7312},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2610.07644. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
We describe the operational infrastructure built to deploy and operate fbnic, a custom multi-host NIC, across hundreds of thousands of production hosts at Meta. Vendor multi-host NICs, designed by retrofitting single-host architectures, suffered from shared firmware and buffers that created cascading isolation failures over seven years. fbnic eliminates these through physical isolation, but shifting to in-house hardware shifts the entire operational burden to the hyperscaler. We present a hardware-in-the-loop CI pipeline testing firmware, driver, and kernel cross-products; a unified observability pipeline co-locating NIC and switch counters for cross-layer fault attribution; a driver-first architecture with fewer than ten firmware message types; a targeted firmware upgrade orchestrator at sub-sled granularity; and scoped repair automation confining blast radius to individual host slices. Over ten months, fbnic achieved a 12X reduction in unplanned unavailability, 37% lower mean time to repair, and 2.3X fewer hardware swaps compared to vendor NICs on the same platform. Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.AR, nuovi lavori del giorno). Categorie arXiv: Networking and Internet Architecture (cs.NI) ; Hardware Architecture (cs.AR). Pagina del lavoro: https://arxiv.org/abs/2610.07644 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-07T11:16:09.469Z dalla pagina https://arxiv.org/list/cs.AR/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).