Re: [ovs-dev] patchwork

> On Nov 10, 2016, at 9:54 PM, Ben Pfaff wrote: > > On Fri, Nov 11, 2016 at 09:11:48AM +0800, Jeremy Kerr wrote: > >>> Jeremy, do we have the right email address subscribed to get patches >>> into OVS patchwork? We've moved around our mailing lists a bit (from >>> our own

[ovs-dev] [PATCH 3/3] netdev-dpdk: Restore flags of dpdk netdev

If the eth device starts failed or vhost port is not running, the flags of dpdk netdev should be restored. Signed-off-by: Binbin Xu --- lib/netdev-dpdk.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c index

Re: [ovs-dev] conditional monitoring

Hi Ben The V6 rebase went to the mailing list on Nov. 4, labelled [patch_v6] ovn: Add datapaths of interest filtering. I don’t see it in patchwork, but I guess that is expected, at that moment. In the interim, the following conflicting commit went in: "Add support for specifying SSL

Re: [ovs-dev] patchwork

Hi Ben, Just so that I understand it correctly, you're using the instance on patchwork.ozlabs.org, right? > Jeremy, do we have the right email address subscribed to get patches > into OVS patchwork? We've moved around our mailing lists a bit (from > our own hosting to Linux Foundation) and it

[ovs-dev] conditional monitoring

Hi Darrell and Liran. I was pleased to hear that you arrived at consensus at ovscon over the conditional monitoring patches. Can you remind me which patch is the one that should go in? (Will a new one be posted?) Thanks, Ben. ___ dev mailing list

Re: [ovs-dev] [PATCH 2/3] util: Use vlog for ovs_abort().

On Thu, Nov 10, 2016 at 02:55:15PM -0800, Joe Stringer wrote: > On 10 November 2016 at 13:42, Ben Pfaff wrote: > > On Thu, Nov 10, 2016 at 01:28:22PM -0800, Joe Stringer wrote: > >> Previously, if vswitchd aborted then the log message would only be > >> printed to stderr, which may

[ovs-dev] [PATCH v3 2/3] ovn-sbctl: commands for managing connection configuration

Add ovn-sbctl commands to manage connection target configuration, including read-only connection attributes. Since there is now a valid reason to use this utility in production environments, Remove statement that this should not be used in production from man page and run-time help text. Added

[ovs-dev] [PATCH v3 1/3] ovn-sb: add SSL configuration to southbound db schema

Augment OVN southbound database schema to allow SSL connection configuration information to be stored and managed within the southbound database. Signed-off-by: Lance Richardson --- ovn/ovn-sb.ovsschema | 21 ++--- ovn/ovn-sb.xml | 48

[ovs-dev] Que hacer ante una Crisis Financiera

Seguridad y validez para sus transacciones financieras Gestión de Tesorería: Importancia ante una Crisis Financiera 24 de Noviembre - Zona Reforma (Ciudad de México) - 9:00 a 20:00 hrs. Imparte: C.P. Fernando García Zárate. . La optimización de costos y la reingeniería de procesos le

Re: [ovs-dev] [PATCH] ovn-trace: Print stage name even without match.

On Thu, Nov 10, 2016 at 03:54:16PM -0500, Russell Bryant wrote: > Given a simple OVN configuration and a sample packet that fails to match > an L2 destination lookup flow, the output of ovn-trace looks something > like this: > > $ ovn-trace --detailed sw0 'inport == "sw0-port1" && eth.src ==

Re: [ovs-dev] [PATCH v4 1/3] Windows: Add internal switch port per OVS bridge

On 7 November 2016 at 13:47, Sairam Venugopal wrote: > I had acked it earlier. Will re-ack that patch if needed. > Sai, I meant v5 of the series and not patch 5. I guess, that was the confusion? It is here: https://patchwork.ozlabs.org/patch/669585/ > > Thanks, > Sairam > >

[ovs-dev] [PATCH net-next v13 4/8] openvswitch: support MPLS push and pop for L3 packets

Update Ethernet header only if there is one. Signed-off-by: Jiri Benc Acked-by: Pravin B Shelar --- net/openvswitch/actions.c | 18 +++--- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/net/openvswitch/actions.c

[ovs-dev] [PATCH net-next v13 3/8] openvswitch: pass mac_proto to ovs_vport_send

We'll need it to alter packets sent to ARPHRD_NONE interfaces. Change do_output() to use the actual L2 header size of the packet when deciding on the minimum cutlen. The assumption here is that what matters is not the output interface hard_header_len but rather the L2 header of the particular

[ovs-dev] [PATCH net-next v13 1/8] openvswitch: use hard_header_len instead of hardcoded ETH_HLEN

On tx, use hard_header_len while deciding whether to refragment or drop the packet. That way, all combinations are calculated correctly: * L2 packet going to L2 interface (the L2 header len is subtracted), * L2 packet going to L3 interface (the L2 header is included in the packet lenght), * L3