Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

One build multiple ASICs

オープン
  • 何か問題がありますか？
#355 コメント 1 件 リアクション 1 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@cfzimmerman がすでに取り組んでいます。

2026年9月4日 から。

評価

この issue はまだ評価されていません。

説明

Dendrite currently supports multiple ASICs

  • Tofino: The Tofino 2 ASIC
  • Tofino Stub: mocks responses, keeps some state, no data plane
  • Softnpu: A virtual ASIC that runs in hypervisors and as a standalone software data plane.
  • Chaos: similar to tofino stub but probabilistically returns errors, primarily used for testing error handling in complex/compound operations that require many underlying ASIC operations.

Each of these ASICs lives within their own cargo feature, meaning dendrite is always compiled for a particular ASIC. This makes a lot of sense for the ASICs we have today. Only one is for production use and everything else is for testing. However there are two factors motivating a rethink.

  1. We have new production ASIC coming on the scene with the X2
  2. There is a desire to package and treat softnpu as a first class ASIC for e2e testing environments (see the discussion in omicron#11133).

It's worth noting that a single dpd will likely never be managing multiple switch ASICs at once (much less multiple different switch ASICs at once), so the compile time choice of ASIC is still a reasonable path forward from that perspective. We could package and deliver multiple dpd binaries, and it would be the responsibility of the control plane to detect what hardware is present and launch the correct dpd daemon. However, that seems like a complexity leak. If Dendrite is responsible for managing and abstracting switching hardware, then we should not be punting on detection responsibility.

One could imagine a meta-daemon of some kind that is responsible for hardware detection and launching the correct type of dpd binary for the ASIC in play. However at that point we're probably at a comparable amount of work to having a single dpd binary that can handle multiple ASICs. Having one less daemon to manage is definitely a benefit. Another benefit of this approach is that fracturing the codebase over cargo features per ASIC is a bit cumbersome to deal with. It would be nice to have cargo check/build/nextest and the LSP just operating over the whole codebase rather than having to do everything multiple times and constantly reconfigure the LSP for work that touches multiple ASICs.

With all the above considerations, I think we should be moving toward a one build multiple ASIC approach. For softnpu in the near term and for X2 in the medium term.

主要言語
Rust
スター
21
フォーク
3
平均マージ
8時間 29分
マージ済み PR（30日）
2

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

oxidecomputer/dendrite のほかの issue

oxidecomputer/dendrite の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。