[ovs-dev] [PATCH] FAQ: Describe how to add new OpenFlow messages.

Jarno Rajahalme jrajahalme at nicira.com
Fri Feb 21 01:10:55 UTC 2014


> On Jan 21, 2014, at 9:34 AM, Ben Pfaff <blp at nicira.com> wrote:
> 
> Signed-off-by: Ben Pfaff <blp at nicira.com>
> ---
> FAQ |   17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
> 
> diff --git a/FAQ b/FAQ
> index 75d9e6b..dac8fe1 100644
> --- a/FAQ
> +++ b/FAQ
> @@ -1454,6 +1454,23 @@ A: These flows drop the ARP packets that IP hosts use to establish IP
>       priority=5,in_port=1,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00,actions=2
>       priority=5,in_port=2,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00,actions=1
> 
> +
> +Development
> +-----------
> +
> +Q: How do I implement a new OpenFlow message?
> +
> +A: Add your new message to "enum ofpraw" and "enum ofptype" in
> +   lib/ofp-msgs.h, following the existing pattern, then recompile and
> +   fix all of the new warnings.

I would add here something like this:

", implementing new functionality for the new message as needed."

Acked-by: Jarno Rajahalme <jrajahalme at nicira.com>

>  (If you configure with
> +   --enable-Werror, as described in INSTALL, then it is impossible to
> +   miss any warnings.)
> +
> +   If you need to add an OpenFlow vendor extension message for a
> +   vendor that doesn't yet have any extension messages, then you will
> +   also need to edit build-aux/extract-ofp-msgs.
> +
> +
> Contact 
> -------
> 
> -- 
> 1.7.10.4
> 
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev



More information about the dev mailing list