NFV (Network functions virtualization)

Intel Aims to Cut NFV Latency

Wind River Systems Inc., the longtime embedded-software company owned by Intel Corp., released software Tuesday that it claims adds a carrier-grade touch that network virtualization has been lacking.

The Open Virtualization Profile (OVP), as it's called, is part of a dedicated push by Intel into network functions virtualization (NFV) and software-defined networking (SDN).

It's a virtualization add-on to Wind River's embedded Linux software. OVP does things like provision and migrate virtual machines -- but it's also got a twist aimed at carriers.

So far, virtualization software has been developed with the data center in mind, aiming to maximize throughput. But running the traffic through hypervisors and virtual switches -- extra elements of software -- adds latency that's not present in a hardware-centric network, says Davide Ricci, Wind River's product line manager.

The difference in timing can be about 700 microseconds, worst-case. For many data-center applications, that's as negligible as adding one more brown M&M to the bowl. But carriers, just like certain rock bands, get really bothered knowing that extra latency is in there, Ricci says.

"That's the big deal. In the physical world, there's no context switch, but in the virtual world, the context switch is a part of the system that introduces latency," Ricci says, with "context switch" being the phrase for the traversing of software elements such as the hypervisor or virtual switch.

This can be fixed by letting software pre-empt whatever the hypervisor is doing. So, that's what Wind River did: OVP adds a pre-empting capability to KVM, an open-source hypervisor.

OVP can shrink the worst-case delay to "well below 15" microseconds, with average delays being more like 3 or 4 microseconds, Ricci says.

Why this matters
OVP adds to Intel's NFV-related arsenal, which includes reference designs for switches and virtual switches, introduced in April. NFV provides a rich opportunity for processor vendors, and Intel seems determined not to blow its chance here.

For more

— Craig Matsumoto, Managing Editor, Light Reading

Burin 1/22/2014 | 5:34:58 AM
re: Intel Aims to Cut NFV Latency will this be considered as industry standard where operator can avoid vendor locked-in as well as to ensure application portability?
JVerity 7/1/2013 | 1:10:50 AM
re: Intel Aims to Cut NFV Latency this sounds like something they might be able to sell to the Wall St. folks doing low-latency trading, too.
I woud think Intel could add some instructions to its processors thayt might help, too.
Craig Matsumoto 6/25/2013 | 5:40:42 PM
re: Intel Aims to Cut NFV Latency Not so much... it's more a way of bypassing a latency tax you get when handing off from one software entity to another. It's a small and specific thing, but it's an indication of how seriously Intel takes NFV, and by extension, how much they have to pay attention to carrier-grade details.
nuker 6/25/2013 | 2:41:21 PM
re: Intel Aims to Cut NFV Latency Is this to enable more compute intensive operations in the hypervisor ?
Sign In