By Sagar Shankaran, Founder of CallSphere
Learn what data processing units (DPUs) do, how they offload networking and security tasks from CPUs and GPUs, and why they are becoming essential in AI data center architectures.
Key takeaways
For decades, data centers ran on two types of processors: CPUs for general computation and GPUs for parallel workloads. But as networks grew faster, security requirements became more complex, and storage systems demanded more intelligence, a growing share of CPU cycles was consumed by infrastructure tasks rather than application workloads.
Data processing units represent a fundamental rethinking of how data center infrastructure work gets done. A DPU is a programmable processor purpose-built to handle the networking, storage, and security functions that were previously performed by the CPU — freeing the CPU (and, by extension, the GPU) to focus exclusively on the application workload that generates business value.
The impact is particularly significant in AI data centers, where every CPU cycle wasted on infrastructure overhead is a cycle not spent feeding data to expensive accelerators.
A modern DPU combines several functional blocks into a single device, typically deployed as a PCIe card or integrated directly onto the server motherboard.
flowchart LR
CALLER(["Caller"])
subgraph TEL["Telephony"]
SIP["Twilio SIP and PSTN"]
end
subgraph BRAIN["Business AI Agent"]
STT["Streaming STT<br/>Deepgram or Whisper"]
NLU{"Intent and<br/>Entity Extraction"}
TOOLS["Tool Calls"]
TTS["Streaming TTS<br/>ElevenLabs or Rime"]
end
subgraph DATA["Live Data Plane"]
CRM[("CRM and Notes")]
CAL[("Calendar and<br/>Schedule")]
KB[("Knowledge Base<br/>and Policies")]
end
subgraph OUT["Outcomes"]
O1(["Booking captured"])
O2(["CRM record created"])
O3(["Human handoff"])
end
CALLER --> SIP --> STT --> NLU
NLU -->|Lookup| TOOLS
TOOLS <--> CRM
TOOLS <--> CAL
TOOLS <--> KB
NLU --> TTS --> SIP --> CALLER
NLU -->|Resolved| O1
NLU -->|Schedule| O2
NLU -->|Escalate| O3
style CALLER fill:#f1f5f9,stroke:#64748b,color:#0f172a
style NLU fill:#4f46e5,stroke:#4338ca,color:#fff
style O1 fill:#059669,stroke:#047857,color:#fff
style O2 fill:#0ea5e9,stroke:#0369a1,color:#fff
style O3 fill:#f59e0b,stroke:#d97706,color:#1f2937
The most visible function of a DPU is advanced network processing. At 100-400 Gbps line rates, traditional software-based networking on the CPU cannot keep up. A DPU handles:
DPUs accelerate storage operations through:
Perhaps the most strategically important function of DPUs is infrastructure security:
A modern DPU contains several specialized processing elements:
| Component | Function | Why Specialized Hardware |
|---|---|---|
| ARM/RISC-V cores | Run infrastructure software (networking stack, storage drivers) | General-purpose but low-power, dedicated to infrastructure |
| Programmable packet processor | Handle network packet processing at line speed | CPU cannot process packets at 400 Gbps |
| Crypto engine | Perform encryption/decryption | AES-256 at 400 Gbps requires dedicated silicon |
| Compression engine | Inline data compression | Software compression cannot match wire speed |
| RegEx/DPI engine | Deep packet inspection, pattern matching | Used for security and traffic classification |
| Memory subsystem | 16-64 GB dedicated DDR | Infrastructure state (flow tables, routing tables) does not compete with application memory |
The key insight is that a DPU is not simply a small CPU grafted onto a network card. Its processing elements are purpose-designed for the specific operations that data center infrastructure requires. A packet processor handles millions of packets per second using match-action tables — something a general-purpose CPU could do in theory but not at the required throughput.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
In an AI training server, the CPU has an important job: preparing training data. It reads raw data from storage, applies preprocessing transforms (tokenization, augmentation, normalization), and fills buffers that the accelerators consume. If the CPU is also handling network packet processing, storage I/O management, and security enforcement, it may not keep up with data preparation — creating a bottleneck that leaves expensive accelerators idle.
By offloading infrastructure functions to the DPU, the CPU's full capacity is available for data pipeline work. In practice, this can improve effective training throughput by 10-20% on workloads that were previously CPU-bottlenecked.
Traditionally, cloud providers imposed a performance overhead through virtualization — hypervisors, virtual switches, and software-defined networking consumed 5-15% of server resources. DPU-based architectures run the entire virtualization and networking stack on the DPU, giving tenants bare-metal performance while maintaining the provider's ability to manage and isolate infrastructure.
This is particularly valuable for AI workloads because:
Distributed AI training relies heavily on RDMA for efficient inter-node communication. DPUs enhance RDMA performance through:
Adaptive routing: When multiple network paths exist between two nodes, the DPU dynamically selects the least congested path for each message. This is critical in large-scale training where thousands of nodes perform all-reduce operations simultaneously, creating complex traffic patterns.
In-network computation: Advanced DPUs can perform reduction operations (summing gradients from multiple sources) within the network fabric itself, reducing the amount of data that must traverse the full network path. This technique, called in-network aggregation, can reduce all-reduce communication time by 2-3x for specific topologies.
Congestion control: DPUs implement sophisticated congestion control algorithms tuned for the bursty, synchronized communication patterns of distributed training. Standard TCP congestion control algorithms perform poorly under these conditions because they were designed for the asynchronous, independent traffic patterns of web browsing and file transfers.
DPU hardware capabilities are only useful with the right software stack:
DPUs run a dedicated infrastructure operating system — typically a hardened Linux distribution — that manages all infrastructure services. This OS is independent of the host server's operating system, creating a clean separation between infrastructure management and application workloads.
The infrastructure OS handles:
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
Developers program DPU data path operations using domain-specific frameworks:
With DPUs handling infrastructure, server management changes fundamentally:
Out-of-band management: DPUs can manage servers even when the host CPU is offline or the host operating system has crashed. Firmware updates, diagnostics, and remote restart work through the DPU's independent management interface.
Zero-trust infrastructure: Because the DPU controls all network access to and from the server, it can enforce security policies regardless of host OS state. A compromised server cannot exfiltrate data or attack other servers because all traffic passes through DPU-enforced security rules.
Fleet-level consistency: DPU firmware and configuration can be managed centrally, ensuring that every server in a fleet enforces identical network, storage, and security policies without relying on host-level configuration that might drift over time.
The economic argument for DPUs is straightforward: specialized hardware performing infrastructure tasks at lower power and higher throughput than general-purpose CPUs reduces the total cost of data center operations. In AI data centers where accelerators represent the dominant capital cost, ensuring those accelerators achieve maximum utilization through DPU-enabled infrastructure optimization provides a direct return on investment.
DPUs are evolving rapidly. Next-generation devices will integrate larger network processing capabilities (800 Gbps and beyond), more sophisticated security engines, and AI-specific acceleration for collective communications. The line between "network card" and "infrastructure processor" will continue to blur as DPUs take on more of the undifferentiated heavy lifting that keeps modern data centers running.
For infrastructure architects planning AI deployments, DPUs are no longer optional components — they are foundational elements that determine how effectively expensive compute resources can be utilized.
A data processing unit (DPU) is a programmable processor purpose-built to handle networking, storage, and security functions that were previously performed by the server's CPU, freeing CPUs and GPUs to focus on application workloads. DPUs combine network processing at 100-400 Gbps line rates, hardware-accelerated encryption, storage protocol handling, and programmable packet processing into a single device. They represent the third pillar of data center computing alongside CPUs and GPUs.
DPUs improve AI performance by offloading infrastructure overhead from CPUs, which would otherwise spend 20-30% of their cycles on networking, storage, and security tasks instead of feeding data to expensive GPU accelerators. By handling RDMA operations, NVMe storage protocols, and encryption in dedicated hardware, DPUs ensure that accelerators achieve maximum utilization. In AI training clusters where GPU-hours cost hundreds of dollars, even a 5-10% improvement in accelerator utilization delivers significant return on the DPU investment.
While SmartNICs and DPUs both handle network offload, a DPU is a fully programmable system-on-chip with its own CPU cores, memory, and operating system capable of running complex infrastructure services independently. SmartNICs typically accelerate specific network functions like packet filtering and checksum offload, whereas DPUs can run complete software-defined networking stacks, storage controllers, and security engines. The evolution from SmartNIC to DPU reflects the growing complexity of infrastructure tasks that must be isolated from the host operating system.
DPUs provide a hardware-enforced security boundary because they control all network and storage access to and from the server, enabling zero-trust security policies that remain effective even if the host operating system is compromised. A compromised server cannot exfiltrate data or attack other servers because all traffic must pass through DPU-enforced security rules. DPU firmware and configuration can be managed centrally across an entire fleet, ensuring consistent security policy enforcement without relying on host-level configuration that might drift over time.

Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
How generative AI produces verified dbt models for data migration — from scratch and incrementally — with SME validation and strict data governance.
See how Circini's automated incident management pipeline turns alert emails into triaged Jira tickets using Snowflake Cortex AI, GPT-4.1, Airflow & MS Teams.
Anthropic's Claude Fable 5 and Mythos 5 explained: pricing, availability, frontier benchmarks, the dual-model safeguard architecture, and what they mean for AI agents.
Where Claude Code, MCP, and multi-agent systems are taking GTM engineering next, and how to prepare your team now for standing and multi-agent workflows.
Where Claude Cowork and the Claude agent ecosystem are heading next — standing agents, MCP, skills as a moat — and the concrete moves to prepare your team now.
The metrics, leading signals, and anti-metrics that prove Claude Cowork is working — acceptance rate, time-to-outcome, and why usage counts mislead.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI