On 08/06/2021 21:07, Flavio Leitner wrote:
>
> Hi Mark,
>
> This looks good to me.
>
> Since the new scheme doesn't allow users to change the number
> of handlers, we must update ovs-vswitchd.conf.db(5) as well.
I updated this documentation
>
> Some comments below.
>
> On Fri, Apr 30, 2021
On 08/06/2021 21:07, Flavio Leitner wrote:
> Hi Mark,
>
> This looks good to me.
>
> Since the new scheme doesn't allow users to change the number
> of handlers, we must update ovs-vswitchd.conf.db(5) as well.
>
> Some comments below.
Thanks for all your reviews. I will work on a v1 of this
Hi Mark,
This looks good to me.
Since the new scheme doesn't allow users to change the number
of handlers, we must update ovs-vswitchd.conf.db(5) as well.
Some comments below.
On Fri, Apr 30, 2021 at 11:31:29AM -0400, Mark Gray wrote:
> The Open vSwitch kernel module uses the upcall
The Open vSwitch kernel module uses the upcall mechanism to send
packets from kernel space to user space when it misses in the kernel
space flow table. The upcall sends packets via a Netlink socket.
Currently, a Netlink socket is created for every vport. In this way,
there is a 1:1 mapping between
