You might start by looking at the Rocker switch implementation which creates
multiple netdev devices for each port of the switch. >> I will look at this
implementation.
In your case you'd
likely create these dummy netdev definitions within you PF driver. My
assumption is that ALL packets woul
I thought of creating one "dummy netdev" per function which will represent each
function in open vswitch. These ports can be treated like logical connection to
the functions. Whenever there is flow-miss in the device, it will punt the
packet to the linux kernel via respective "dummy netdev" and
Hello,
I am working on PF/VF driver for PCI-E based SR-IOV capable card. This device
has got few cpus and ram and is capable of running linux and any linux-userland
application on the device it self. Register layout (for datapath like TX/RX
ring, stats etc.) between host and device is defined by
Thanks Ben.
Mehul.
On Wednesday, December 3, 2014 1:07 AM, Ben Pfaff wrote:
On Tue, Dec 02, 2014 at 10:42:09AM +, Mehul Vora wrote:
> ??I am trying to understand different components of ovs. Please correct me if
> my understanding is wrong,??
> 1. ovsdb-server :
Hello,
I am trying to understand different components of ovs. Please correct me if my
understanding is wrong,
1. ovsdb-server : Maintains openvswtich configuration databse.
2. ovs-vswitchd : Dameon that controls all Open vSwitch swithces on the local
system. When this process is started it ge
