diff options
author | Ben Pfaff <blp@ovn.org> | 2017-03-29 11:25:38 -0700 |
---|---|---|
committer | Ben Pfaff <blp@ovn.org> | 2017-03-30 09:04:10 -0700 |
commit | fc7840a90d3b6ca7edc7daf4ce9357195c206b18 (patch) | |
tree | cf7fad1db9095a5bc128aced4f7b4b006253ba34 /Documentation | |
parent | 692ac4522064021b851c562c1a966b9f89b08efc (diff) | |
download | openvswitch-fc7840a90d3b6ca7edc7daf4ce9357195c206b18.tar.gz |
faq: Expand on answer about packet buffering removal.
Signed-off-by: Ben Pfaff <blp@ovn.org>
Acked-by: Andy Zhou <azhou@ovn.org>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/faq/openflow.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/Documentation/faq/openflow.rst b/Documentation/faq/openflow.rst index 376e64eb4..d21bb4459 100644 --- a/Documentation/faq/openflow.rst +++ b/Documentation/faq/openflow.rst @@ -462,6 +462,15 @@ What's going on? messages and will send an error response if any other value of this field is included in a "packet-out" or a "flow mod" sent by a controller. + Packet buffers have limited usefulness in any case. Table-miss packet-in + messages most commonly pass the first packet in a microflow to the OpenFlow + controller, which then sets up an OpenFlow flow that handles remaining + traffic in the microflow without further controller intervention. In such + a case, the packet that initiates the microflow is in practice usually + small (certainly for TCP), which means that the switch sends the entire + packet to the controller and the buffer only saves a small number of bytes + in the reverse direction. + Q: How does OVS divide flows among buckets in an OpenFlow "select" group? A: In Open vSwitch 2.3 and earlier, Open vSwitch used the destination |