This article focuses on the Open vSwitch (OVS) userspace datapath accelerated with the Data Plane Development Kit (DPDK) and its new feature, partial flow hardware offloading, which can potentially save resources while improving the packet processing rate.
Open vSwitch is growing every day and being used in large-scale deployments. Usually, that means there are few ports configured in the vswitch that will be always available, like physical Ethernet ports and several other ports providing networking connectivity to virtual machines or containers. Those other ports are software devices and very often they cannot be reused after a reboot or a system crash for example. This blog post will talk about how to make sure the vSwitch comes up...
Open vSwitch is a software switch responsible for providing network connectivity to virtual machines or containers. Since it is programmable, it brings a challenge to understand what is going on in the network. Open vSwitch (OVS) is an OpenFlow virtual switch, so before talking about OVS itself, it is necessary to introduce OpenFlow a bit. OpenFlow is an open standard protocol that allows separation of the packet forwarding (data plane) from the high level routing decisions (control plane). The control...
Open vSwitch (OVS) is a virtual switch used in production from small to large scale deployments. It is designed to provide network automation along with support for a number of management interfaces and protocols. However, the developer or the administrator might need to understand more of what is going on under the hoods and OVS does a good job providing a very good logging facility which is the subject of this article. Editor's note: Red Hat Knowledgebase - " What...
Article
