UK’s trusted IT infrastructure partner since 2003
Servnet
ConfiguratorGet in Touch
What is a DPU or SmartNIC? Offloading explained for UK server buyers — analysisWhat is a DPU or SmartNIC? Offloading explained for UK server buyers — analysis — reach
Server Infrastructure · Explainer

What is a DPU or SmartNIC? Offloading explained for UK server buyers

Servnet Editorial · Server Infrastructure Practice9 min read

DPU and SmartNIC appear on more server quotes every year, often without much explanation of what they do or whether you need one. At heart the idea is simple: take work the main CPU used to do for the network, storage and security, and run it on a dedicated processor on the network card instead. This explainer sets out what a DPU and a SmartNIC actually are, what they offload, and when that offload is worth paying for in a UK server build.

Work offloaded to a DPU
4ApplicationsKeep host cores - the paying work3SecurityEncryption - microsegmentation2StorageNVMe-oF - protocol offload1NetworkingOverlay - switching - routing

From NIC to SmartNIC to DPU

An ordinary network card moves packets and hands everything else to the host CPU. A SmartNIC adds programmable offload, taking on tasks such as overlay networking, encryption and packet filtering that would otherwise burn host cycles. A DPU, or data processing unit, goes further: it is effectively a small computer on the card, with its own cores, memory and operating system, capable of running networking, storage and security services independently of the host.

The line between a capable SmartNIC and a DPU is more a spectrum than a hard boundary, but the direction is consistent. Each step moves infrastructure work off the main CPU and onto purpose-built silicon that does it more efficiently and in isolation from the workloads the server is meant to run.

What actually gets offloaded

The work a DPU or SmartNIC takes on falls into three buckets. Networking offload handles overlay encapsulation, switching and routing for virtual networks that would otherwise consume host cores. Storage offload presents and accelerates remote storage, including NVMe over fabrics, so the host sees fast storage without spending CPU on the protocol. Security offload runs encryption, microsegmentation and packet inspection on the card, isolated from the host it protects.

The common thread is the infrastructure layer beneath the applications. Freeing the host CPU from that plumbing returns cores to the paying workload and, in the security case, creates a control point that sits outside the host's own operating system. Our network card guidance covers where these capabilities sit in the wider NIC range.

The vSphere DPU case

The most concrete mainstream example is in virtualisation. VMware's distributed services engine runs parts of the hypervisor's networking and security on a DPU rather than the host CPU, so the cores you licence and pay for go to virtual machines instead of to switching and firewalling. For a busy virtualisation host that is a direct return: more usable consolidation from the same silicon, and infrastructure services isolated from the workloads.

That illustrates the general rule. A DPU pays off where the host is spending a meaningful share of its cores on infrastructure rather than the application, because the offload converts that overhead back into useful capacity. Where the host barely touches that plumbing, the DPU is solving a problem you do not have. Our VMware vSAN page covers the surrounding platform context.

DPU in the data and control plane
PCIeHost CPUruns VMsDPU / NICown OSNetworkfabricStorageNVMe-oFSecurityenforced

When you actually need one

DPUs and SmartNICs earn their place at scale and in specific roles, not on every server. The strong cases are dense virtualisation where infrastructure overhead is eating consolidation, high-throughput networking where host-based packet processing has become the bottleneck, disaggregated storage over fabrics, and zero-trust designs that want security enforced outside the host. In those settings the offload is a genuine efficiency and architecture win.

For a single general-purpose server with modest networking, a standard NIC is the right and cheaper choice. The honest test is whether infrastructure work is consuming host resources you would rather spend on the workload; if it is not, you do not yet need a DPU.

  • Standard NIC: moves packets, hands everything else to the host CPU
  • SmartNIC: programmable offload of networking, encryption and filtering
  • DPU: a computer on the card running networking, storage and security independently
  • Worth it for dense virtualisation, high-throughput networking, fabric storage and zero-trust
  • A standard NIC is the right choice for a modest single server

Where it fits in a build

If your design hits one of the strong cases, the DPU or SmartNIC is specified like any other component, matched to the platform and the workload. If it does not, a conventional NIC keeps the build simpler and cheaper. Size the choice against the role using our network card guidance, and bring the requirements to our server configuration service and we will tell you honestly whether an offload card belongs in your build.

Key takeaways
  • A SmartNIC adds programmable offload; a DPU is effectively a computer on the card.
  • They offload networking, storage and security work from the host CPU.
  • In vSphere, a DPU runs hypervisor networking and security so licensed cores go to VMs.
  • They pay off at scale: dense virtualisation, high-throughput networking, fabric storage, zero-trust.
  • A standard NIC remains the right, cheaper choice for a modest single server.
Frequently asked

FAQs — What is a DPU or SmartNIC? Offloading explained for UK server buyers

Basics

What is the difference between a SmartNIC and a DPU?

A SmartNIC adds programmable offload of networking, encryption and filtering to a network card. A DPU goes further - its own cores, memory and operating system let it run networking, storage and security independently of the host. Both move infrastructure work off the main CPU. See our NIC guidance.

Buying

Do I need a DPU in my server?

Only if infrastructure work is consuming host cores you would rather spend on the workload - dense virtualisation, high-throughput networking, fabric storage or zero-trust. For a modest single server a standard NIC is right and cheaper. We will advise honestly in our configuration service.

How does a DPU help a VMware host?

VMware can run parts of the hypervisor's networking and security on a DPU instead of the host CPU, so the cores you licence go to virtual machines rather than switching and firewalling. That lifts usable consolidation. See the platform context on our VMware vSAN page.

Related

Continue reading

More in Explainers

Got a question this article didn't answer?

One conversation with an engineer who's done this before. No sales script.

Talk to Servnet →