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 "dum
> 2. I saw a new "netlink" interface added to add flows/actions to the switch
> device. Does ovs-ofctl usethis new netlink to add flows to the hardware? Or
> is there any other utility to do the same?
By the way, John cc'ed, is also working on this. He might have some thoughts
>
> Thanks,Mehul.
>
> 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 n
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
