{"id":15090,"date":"2025-09-23T09:35:59","date_gmt":"2025-09-23T16:35:59","guid":{"rendered":"https:\/\/mattfife.com\/?p=15090"},"modified":"2025-09-11T09:46:51","modified_gmt":"2025-09-11T16:46:51","slug":"scalable-io-vs-sr-iov-virtualization","status":"publish","type":"post","link":"https:\/\/mattfife.com\/?p=15090","title":{"rendered":"Scalable IO vs SR-IOV Virtualization"},"content":{"rendered":"\n

Are the days of SR-IOV (Single Root I\/O Virtualization) numbered? SR-IOV was originally designed for 20 or so VMs with most instances using 8 vCPUs or less. Now that we have 60-128 cores\/120-256 hw threads and beyond with multiple sockets and CXL<\/a>, things have changed.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Scalable IO offers better scalability, flexibility, over-provisioning, and a Scalable IO system can still support traditional SR-IOV in backwards compatibility mode.<\/p>\n\n\n\n

It does this with hardware-assisted, efficient routing and has different modes for direct and intercepted path functionality. I won’t claim I fully grock all the details, but it does seem like a great way to start taking advantage of newer architecture enhancements we’re seeing in a wide variety of upcoming hardware platforms.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Give the spec a read to learn more.<\/p>\n\n\n\n

Links:<\/p>\n\n\n\n