Signed-off-by: Ben Pfaff <b...@nicira.com>
---
FAQ.md | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/FAQ.md b/FAQ.md
index 5ee529c..70dfd9c 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -1705,11 +1705,20 @@ A: Add your new message to "enum ofpraw" and "enum
ofptype" in
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. 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.)
+ 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.)
+
+ If you want kernel datapath support for your new field, you also
+ need to modify the kernel module under the datapath/ (the Linux
+ datapath) or datapath-windows/ directory. This isn't mandatory,
+ since fields understood only by userspace work too (with a
+ performance penalty), so it's reasonable to start development
+ without it.
### Q: How do I add support for a new OpenFlow action?
--
1.7.10.4
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
