Reported-by: Enas Ahmad <enas.ah...@kaust.edu.sa>
Signed-off-by: Ben Pfaff <b...@ovn.org>
---
AUTHORS | 1 +
FAQ.md | 11 ++++++-----
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/AUTHORS b/AUTHORS
index 96bdc4f..13b19ca 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -282,6 +282,7 @@ Dhaval Badiani dbadi...@vmware.com
DK Moon dkm...@nicira.com
Edwin Chiu ec...@vmware.com
Eivind Bulie Haanaes
+Enas Ahmad enas.ah...@kaust.edu.sa
Eric Lopez elo...@nicira.com
Frido Roose fr.ro...@gmail.com
Gaetano Catalli gaetano.cata...@gmail.com
diff --git a/FAQ.md b/FAQ.md
index 8bd7ab9..6d1c01b 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -2020,11 +2020,12 @@ A: Add new members for your field to "struct flow" in
lib/flow.h, and
add new enumerations for your new field to "enum mf_field_id" in
lib/meta-flow.h, following the existing pattern. Also, add support
to miniflow_extract() in lib/flow.c for extracting your new field
- from a packet into struct miniflow. Then recompile and fix all of
- the new warnings, implementing new functionality for the new field
- or header as needed. (If you configure with --enable-Werror, as
- described in [INSTALL.md], then it is impossible to miss any
- warnings.)
+ from a packet into struct miniflow, and to nx_put_raw() in
+ lib/nx-match.c to output your new field in OXM matches. Then
+ recompile and fix all of the new warnings, implementing new
+ functionality for the new field or header as needed. (If you
+ configure with --enable-Werror, as described in [INSTALL.md], then
+ it is impossible to miss any warnings.)
If you want kernel datapath support for your new field, you also
need to modify the kernel module for the operating systems you are
--
2.1.3
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
