[ovs-dev] [PATCH 3/3] lisp: avoid using stale lisp socket.

This patch is similar to earlier vxlan patch. Lisp device close operation frees lisp socket. This operation can race with lisp-xmit function which dereferences lisp socket. Following patch uses RCU mechanism to avoid this situation. Signed-off-by: Pravin B Shelar ---

[ovs-dev] [PATCH 2/3] datapath: backport: geneve: avoid using stale geneve socket.

Upstream commit: commit fceb9c3e38252992bbf1a3028cc2f7b871211533 Author: pravin shelar Date: Fri Oct 28 09:59:16 2016 -0700 geneve: avoid using stale geneve socket. This patch is similar to earlier vxlan patch. Geneve device close operation frees

[ovs-dev] [PATCH 1/3] datapath: backport: vxlan: avoid using stale vxlan socket.

Upstream commit: commit c6fcc4fc5f8b592600c7409e769ab68da0fb1eca Author: pravin shelar Date: Fri Oct 28 09:59:15 2016 -0700 vxlan: avoid using stale vxlan socket. When vxlan device is closed vxlan socket is freed. This operation can race with

Re: [ovs-dev] [PATCH 15/15] trivial: Resolve whitespace issues with acinclude

On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane wrote: > Completely unrelated, but annoying. Let's fix it up. > > Signed-off-by: Stephen Finucane > applied to master. I believe I applied all of this series except for the changes to DESIGN. There were

Re: [ovs-dev] [PATCH 14/15] doc: Convert FAQ to rST

On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane wrote: > Signed-off-by: Stephen Finucane > Applied to master with a couple small changes: diff --git a/FAQ.rst b/FAQ.rst index 328e87a..de7aaf7 100644 --- a/FAQ.rst +++ b/FAQ.rst @@ -124,7 +124,7 @@ Q:

Re: [ovs-dev] [PATCH 12/15] doc: Convert OPENFLOW-1.1+ to rST

On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane wrote: > Rename it to OPENFLOW. > > Signed-off-by: Stephen Finucane > I have applied patches 11 and 12 to master. -- Russell Bryant ___ dev mailing list

Re: [ovs-dev] [PATCH 13/15] doc: Convert DESIGN to rST

On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane wrote: > +OpenFlow 1.0 > + > + > + === == == == == > +MODIFYDELETE > + ADD MODIFY

Re: [ovs-dev] [PATCH 13/15] doc: Convert DESIGN to rST

On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane wrote: > -``` > - master/ > - message and reason code other slave > - ---- > - OFPT_PACKET_IN /

Re: [ovs-dev] [PATCH 10/15] doc: Convert README-native-tunneling to rST

On Sat, Oct 29, 2016 at 1:50 PM, Stephen Finucane wrote: > On 28 Oct 23:25, Russell Bryant wrote: > > On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane > > wrote: > > > > > Signed-off-by: Stephen Finucane > > > --- > > > Makefile.am

[ovs-dev] [PATCH] release: Propose a shorter release cycle for 2.7.

OVS recently adopted a six month release cycle. OVS doesn't have to align to other projects, but it can be beneficial. The dates for OVS 2.6 aligned very well to OpenStack, which is a major consumer of OVS that usually does 6 month releases. OpenStack is doing a short release cycle for its Ocata

Re: [ovs-dev] [PATCH 10/15] doc: Convert README-native-tunneling to rST

On 28 Oct 23:25, Russell Bryant wrote: > On Tue, Oct 18, 2016 at 10:03 PM, Stephen Finucane > wrote: > > > Signed-off-by: Stephen Finucane > > --- > > Makefile.am | 2 +- > > README-native-tunneling.md | 85 --- >

Re: [ovs-dev] [PATCH RFC v4 2/3] netdev-dpdk: Arbitrary 'dpdk' port naming

On 28 Oct 15:45, Ciara Loftus wrote: > 'dpdk' ports no longer have naming restrictions. Now, instead > of specifying the dpdk port ID as part of the name, the PCI > address of the device must be specified via the 'dpdk-devargs' > option. eg. > > ovs-vsctl add-port br0 my-port > ovs-vsctl set