[ovs-dev] [PATCH 2/2] flow: P4 based hash calculation on IP and Ethernet headers

From: Cian Ferriter Replaces miniflow_hash_5tuple() with miniflow_hash_ntuple() which calls the dynamically generated OVS_HASH_FIELDS macro. This macro is generated at the configure stage of OVS compilation and depends on the standard header fields in the P4 input file.

[ovs-dev] [PATCH 0/2] P4 support in OVS

--with-dpdk=$DPDK_BUILD p4inputfile= $ make --- Cian Ferriter (1): flow: P4 based hash calculation on IP and Ethernet headers Muhammad Shahbaz (1): adding P4 support acinclude.m4 | 17 +++ build-aux/extract-ofp-actions | 4 +- build

[ovs-dev] [PATCH 1/2] adding P4 support

This adds necessary changes in the OVS codebase to consume the C (macro) code generated by the OVS plugin in p4c-behavioral. It also updates the OVS build system to take a P4 program as input at 'configure' time. --- acinclude.m4 | 17 +++

[ovs-dev] [PATCH for p4c-behavioral 2/2] Add 'hash.c.h' file to support P4 based hash calculation

From: Cian Ferriter As a first pass, all standard header fields defined in the P4 input file are hashed. This file uses the bit_width of each field similar to the packets.h.h file to decide between calling the 32bit or 64bit OVS hashing function. This implementation was

[ovs-dev] [PATCH for p4c-behavioral 1/2] Adding OVS plugin

This adds a new plugin, called OVS, in p4c-behavioral. Given a P4 program, the plugin generates a set of C (macro) code which is called at different locations within the OVS codebase. The code under the plugin folder reflects the same directory structure and files in which they are called in the

[ovs-dev] [PATCH for p4c-behavioral 0/2] P4 support in OVS

-behavioral. The current changes are for the userspace OVS implementation which can run with DPDK. To test these changes, you can run the following command: $ ./p4c-behavioral --gen-dir --plugin ovs --- Cian Ferriter (1): Add 'hash.c.h' file to support P4 based hash calculation Muhammad Shahbaz

Re: [ovs-dev] [PATCH v2] Introducing support for P4 in OVS

t; easier to follow than the indirection through a separate directory plus > > an extra nested #include. > > > > I'll certainly have other comments, but I spent all afternoon on this > > and I'm out of time for the day. > > > > What do you think of t

Re: [ovs-dev] [PATCH v2] Introducing support for P4 in OVS

fields at different places in the code, i.e., in bfd.c, cfm.c, and more, with the P4 fields. I'm working on a patch for this and will share on the dev-list, soon. Thanks, Shahbaz On Fri, Oct 14, 2016 at 8:56 PM Muhammad Shahbaz <mshah...@cs.princeton.edu> wrote: > Hi Ben, > > That'