Hi. I'm MJay, from Intel. In this video, I'm going to introduce the DPDK framework, a new feature of DPDK that abstracts lower-level features and helps you seamlessly take advantage of DPDK innovations faster in your development. 

The benefit you get is the portability of your development across multiple devices and accelerators, architectures, and generations. In today's cloud environment, you might not know what devices are present on a platform. So this is a critical feature. 

DPDK started simple, with Ethernet devices. Today, with a flex of innovation, DPDK has expanded to support additional devices like crypto, compression, SoC, FPGA, and additional accelerators. Right now, developers often face challenges when porting their software to this continuously evolving scenario. And that can be really limiting. 

Let's give an example. Let's say a developer wants to deliver a QoS application on top of DPDK. Let's assume they do not follow the framework, and they chose to support only one particular device in that product. Once they are done developing the product, and they start shipping the products to the client, they learn that the clients are requesting to use different devices other than the one the developer chose. 

This is not good for the developer. If their client insist that they want to use a different device, now the developer has to start porting all over again. If the developer would have used a DPDK framework, they would have had a much easier time. 

DPDK supports multiple devices from multiple vendors, and each device has its own unique interface with this QoS functionality. That's the problem the DPDK framework solves. The DPDK framework addresses the community's need for an abstraction framework. This abstraction improves agility and portability for the NFV community. 

The main advantage of DPDK is performance. DPDK framework provides accelerated performance while abstracting users away from the implementation details. In summary, if you write your application to the DPDK framework, your portability is long-lived. There's no longer a need to go under the hood to address specific devices. 

Thanks for watching. Don't forget to access the links provided, to learn more about the DPDK framework and how it can further benefit you.