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

On 06/07/2021 10:05, David Marc hand wrote: > Small nits on the NEWS update. > > On Mon, Jul 5, 2021 at 3:39 PM Mark Gray wrote: >> diff --git a/NEWS b/NEWS >> index a2a2dcf95d7d..80b13e358685 100644 >> --- a/NEWS >> +++ b/NEWS >> @@ -29,7 +29,12 @@ Post-v2.15.0 >> - ovsdb-tool: >> *

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

Small nits on the NEWS update. On Mon, Jul 5, 2021 at 3:39 PM Mark Gray wrote: > diff --git a/NEWS b/NEWS > index a2a2dcf95d7d..80b13e358685 100644 > --- a/NEWS > +++ b/NEWS > @@ -29,7 +29,12 @@ Post-v2.15.0 > - ovsdb-tool: > * New option '--election-timer' to the 'create-cluster'

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

Hi Mark, On Mon, Jul 05, 2021 at 09:38:37AM -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 > space flow table. The upcall sends packets via a Netlink socket. > Currently, a Netlink

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

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