China’s Nebula Matrix S1000 SmartNIC enters the Linux 7.4 kernel
On September 21, 2026 Nebula Matrix’s NBL driver was merged into net-next, clearing the way for mainline support of the 100 Gbps S1000 SmartNIC in Linux 7.4. Operators running these cards in cloud and HPC fleets should plan the move from the out-of-tree driver to the kernel.
September 21, 2026. Nebula Matrix’s NBL driver lands in net-next, the development tree for the kernel’s networking subsystem. Linux 7.4. The S1000 SmartNIC, a 100 Gbps card designed in China, is on track to ship in mainline. Why it matters: a Chinese DPU vendor joins the ranks of official Ethernet drivers, and the operators running these cards can stop maintaining an out-of-tree module.
Nebula Matrix is a Chinese company building SmartNICs and DPUs — data processing units — for data centers. Its m18110 and m18000 products, marketed under the SNIC S1000 range, are 100GE network adapters aimed at cloud computing and HPC. Each card carries up to two 100G interfaces over a PCIe Gen4 x16 slot, covering the features expected of a high-end adapter in that class.
A driver written by the vendor, pushed upstream
The term SmartNIC covers a precise reality: offloading network, storage, and sometimes security functions from the host CPU to free cores for application workloads. On a cloud or HPC node, every cycle spent processing packets is a cycle not running a payload. A 2×100G card like the S1000 is therefore not just a throughput accelerator: it is a way to cut the cost of networking per unit of compute, which makes it a strategic component for large-scale operators.
The detail that matters is not the card but the trajectory of its driver. Nebula Matrix developed NBL in-house and ran the upstreaming process itself to get it accepted into the Linux kernel. The initial driver was merged into net-next in the week before September 21, 2026, which places it in line for the Linux 7.4 merge window.
Until now the company shipped Windows and Linux drivers separately. Mainline support changes the calculus for an operator: the card works at boot on a stock kernel, with no module to compile, no signature to manage, and no breakage on a kernel upgrade. For a team deploying hundreds of nodes, that is the difference between a fleet managed by a standard image and one that requires DKMS plus manual tracking.
Why a Chinese DPU vendor is looking upstream
The move belongs to a wider pattern. DPUs and SmartNICs have become one of the fields where China’s push for technological independence plays out, alongside domestic CPUs and GPUs. Offloading networking, storage, or security from the host CPU to a dedicated card is a strategic capability for cloud and HPC providers — and a market long dominated by Western players.
Historically these drivers have often stayed out-of-tree: NVIDIA (BlueField), Intel (IPU), AMD (Pensando), and Marvell maintain their own stacks with varying degrees of openness. An Ethernet driver merged into net-next signals something else: the vendor accepts the community’s review process, long-term maintenance, and public visibility of its code.
For Nebula Matrix, the stakes are technical and commercial at once. A card whose driver is in the kernel is easier to adopt for a cloud operator, an integrator, or a research center: it blends into Linux distributions without friction. It is the same logic that led the historical NIC vendors — Intel, Broadcom, Mellanox — to maintain mainline drivers for years.
What it changes for operations
For the team managing a node fleet, a mainline driver shows up as recovered engineering days. The typical scenario before Linux 7.4: download the vendor driver, verify its signature, fold it into the image, then recompile it on every kernel bump. The scenario after: the card appears as an ordinary network interface as soon as a 7.4 or later kernel boots.
Two caveats are worth keeping. The first is maturity: a driver that has just entered mainline is rarely equivalent, feature for feature, to the vendor’s own build. Some advanced functions — encryption, storage, or network offload — may arrive later, or stay in the vendor’s tooling. The second is deployment timing: no one runs Linux 7.4 in production on release day. The value materializes as stable distributions catch up to that kernel.
A merged driver is not yet a shipped one. Between net-next and a bootable kernel lie the 7.4 merge window, the release-candidate cycle, and the lag before stable distributions rebase onto it. Read this announcement, then, as a signal of intent rather than an immediate upgrade path: the practical deadline is the first stable Ubuntu, Debian, or RHEL kernel that carries 7.4, and that will land later than the upstream tag. The gap is exactly where a team should do its functional testing, because it is the one window in which the new driver and the old vendor binary can be compared side by side on the same hardware.
The operational decision is easy to state. If you already run S1000 cards with the out-of-tree driver, plan a switch to the mainline driver once Linux 7.4 has stabilized in your distribution, and validate functional equivalence before rolling out. If you are evaluating the card, mainline presence removes a real adoption risk, but confirm that the features you need are covered by the upstream driver rather than a vendor binary.
The mainline driver bar
Entering net-next is not a symbolic trophy; it is a level of rigor. The mainline Ethernet drivers — mlx5 for NVIDIA/Mellanox, bnxt for Broadcom, ice and igc for Intel — are maintained publicly, reviewed by the networking subsystem maintainers, and held to the same compatibility rules as the rest of the kernel. Nebula Matrix is choosing to meet that bar rather than stay a binary distributed on the margins of the kernel.
The move is not isolated either. The same week, Phoronix reported that Linux 7.4 should also pick up the Realtek RTL8127atf and RTL8116af controllers, two workstation-oriented cards. The trend is the same at both ends of the spectrum, from data-center 100G to desktop 2.5G: vendors prefer a driver that lives and dies with the kernel over a binary they must maintain alone, release after release.
What matters for an operator is not the vendor’s nationality but the quality of the upstream maintenance. A merged driver is subject to review by Jakub Kicinski, Paolo Abeni, and the other Linux networking maintainers; regressions are treated as kernel bugs, not vendor support tickets. That guarantee, more than the card itself, is what justifies attention on this merge.
Verdict
Nebula Matrix will not overturn the DPU market in a week, but its NBL driver entering net-next is a structural signal. If you operate S1000 SmartNICs, the move to the Linux 7.4 mainline driver makes your fleet simpler to maintain and safer to upgrade — provided you validate functional equivalence before discarding the out-of-tree module. If you track the NIC market, take the lesson: a vendor that pushes its driver upstream buys a credibility no downloadable binary provides.