News: 1775761421

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Google wants more Intel inside ... its datacenters, taps Chipzilla for more SmartNICs

(2026/04/09)


Google will continue to work with Intel, buying SmartNICs for its public cloud rather than blazing its own trail as AWS has done with its Nitro NICs.

Like most hyperscalers today, Google employs SmartNICs, or as Intel prefers to call them, infrastructure processing units (IPUs). These devices are essentially a computer on a network card and are designed to offload networking, security, and storage operations, freeing up CPU resources for tenant workloads.

While Amazon employs custom ASICs from its Annapurna Labs team and Microsoft uses custom logic running on FPGAs, Google tapped Intel to develop an ASIC-based IPU called [1]Mount Evans , which launched alongside its C3 instances in 2022.

[2]

On Thursday, Intel announced Google had expanded this collaboration to develop new IPUs in a press release that reads like a [3]desperate attempt to convince the public that its Datacenter and Networking divisions are still relevant.

[4]

[5]

Intel CFO David Zinsner had alluded to increased demand for these services during the company's Q4 earnings call in January, [6]touting that the company's custom ASIC biz grew more than 50 percent in 2025 and exited Q4 at an annualized revenue run rate above $1 billion.

Intel didn't elaborate on what Google's next-gen IPUs might look like, but given the demand for high speed networking for AI compute clusters, there's a good chance it'll be significantly faster than its 200 Gbps Mount Evans IPUs.

[7]

Alongside the expanded IPU collab, Intel was also keen to note that the Chocolate Factory wasn't giving up on its Xeon processors, which will power a variety of general purpose and AI workloads. In other words, it is business as usual.

Like many hyperscalers, Google now has its own Arm-based CPU, codenamed [8]Axion , which runs both internal and customer facing workloads.

However, just as Graviton and Cobalt have replaced Xeon or Epyc processors in Amazon's or Microsoft's clouds, neither Intel nor AMD is at risk of being ejected by Axion any time soon.

[9]

In fact, since many customers prefer to run their workloads on x86 cores, either for performance or compatibility reasons, Intel remains useful for putting pricing pressure on AMD and vice versa.

In any case, Intel felt it was necessary to reassure everyone that Xeon remained a key part of Google Cloud, particularly when it comes to AI. But again, this is nothing new.

[10]Peace President's Iran war piles more pain on already battered PC market

[11]Intel gets trapped in Elon's reality distortion field as it joins in megafab delusions

[12]Apple's chips are the core of a new landscape, but its biggest win is Windows

[13]Patch to end i486 support hits Linux kernel merge queue

Xeons have been the CPU of choice for Nvidia's 8-GPU DGX reference designs going back to the H100 in 2022. In other words, many of Google's GPU instances already had Intel inside.

And, while AI workloads also need CPUs to orchestrate agents and execute the code generated by Google's GPUs and TPUs, there's nothing that makes Xeon inherently better for this job than Epyc or Axion. In fact, at cloud scale, the best CPU for agentic AI is probably whatever happens to be sitting idle at any given moment. ®

Get our [14]Tech Resources



[1] https://www.theregister.com/2023/05/23/google_cloud_c3_ipu/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2adghgm8XOs64Vu-YFb8SkgAAAMc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://newsroom.intel.com/data-center/intel-google-deepen-collaboration-to-advance-ai-infrastructure

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44adghgm8XOs64Vu-YFb8SkgAAAMc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33adghgm8XOs64Vu-YFb8SkgAAAMc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://seekingalpha.com/article/4862077-intel-corporation-intc-q4-2025-earnings-call-transcript

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44adghgm8XOs64Vu-YFb8SkgAAAMc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[8] https://www.theregister.com/2025/10/22/google_multi_arch_x86_arm_port/

[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33adghgm8XOs64Vu-YFb8SkgAAAMc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[10] https://www.theregister.com/2026/04/09/middle_east_madness_to_hike/

[11] https://www.theregister.com/2026/04/07/intel_elon_space_delusion/

[12] https://www.theregister.com/2026/04/07/opinion_column_apple_vs_microsoft/

[13] https://www.theregister.com/2026/04/06/patch_to_end_i486_support/

[14] https://whitepapers.theregister.com/



"The eleventh commandment was `Thou Shalt Compute' or `Thou Shalt Not
Compute' -- I forget which."
-- Epigrams in Programming, ACM SIGPLAN Sept. 1982