Re: [ovs-dev] [PATCH v4 3/3] dpif-netlink: Introduce per-cpu upcall dispatch

2021-07-07 Thread Mark Gray
On 06/07/2021 13:35, Flavio Leitner wrote: > > The two functions below are Linux specific, so they need to be conditional > to the #ifdef above like you did in dpif_netlink_recv_wait(): > > #ifdef _WIN32 > dpif_netlink_recv_wait_windows() > #else > dpif_netlink_recv_wait_vport_dispatch() >

Re: [ovs-dev] [PATCH v4 3/3] dpif-netlink: Introduce per-cpu upcall dispatch

2021-07-06 Thread Flavio Leitner
Hi Mark, David had some comments about the NEWS file, and I found an issue on Windows below. On Tue, Jul 06, 2021 at 05:31:11AM -0400, Mark Gray wrote: > The Open vSwitch kernel module uses the upcall mechanism to send > packets from kernel space to user space when it misses in the kernel >

[ovs-dev] [PATCH v4 3/3] dpif-netlink: Introduce per-cpu upcall dispatch

2021-07-06 Thread Mark Gray
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