Network Processor Units (NPU) FTW

Network Processor Units (NPU) FTW

Network processing Units (NPU) for the Win

Cisco-Catalyst-3850-Cavium

About the Author

Brent SalisburyBrent has worked in both the Enterprise and vendor sides. In 2014 Brent left RedHat to be a co-founder of Socketplane.io, a startup with a focus on reliable, scalable and performant Docker networking. In 2015, Docker Inc. acquired Socketplane. Now working at Docker, he is part of an engineering team that is building community and working to make sure the users experience of Docker networking is as satisfying as the rest of the amazing project that is fundamentally changing the infrastructure market as fast as anything the industry has experienced since the micro processor.View all posts by Brent Salisbury →

Guest
2 years 1 month ago


I think the lack of openness has really marginalized NPUs. Years ago I did some programming on the NP4GS3 but there was very little “buzz” around it because it was encrusted in NDAs. There was only one open NPU – the Intel IXP – and so it got 100% of the mindshare in academia even though IMO its architecture sucks. (People said they were doing NPU research but really they were doing IXP research.) Now the “traditional” NPUs have been replaced by MIPS GPNPUs (e.g. Cavium, Raza/NetLogic/Broadcom) which should be easier to program but there’s still zero public discussion and zero cool Github repos because everything is locked away behind NDAs. Even if they have technical advantages, the fact that it costs you ~$100K to find out what they are basically kills innovation. Might as well just use x86 (Intel claims Sandy Bridge can drive 100 Gbps…)

Guest
2 years 1 month ago


Based on the sizes of the heatsinks, it looks like Cavium is doing almost none of the work. http://www.cavium.com/OCTEON-II_CN62XX.html It’s an NPU, but not a very big one.