diff options
| author | Mehak Mahajan <mmahajan@nicira.com> | 2012-06-26 12:30:26 -0700 |
|---|---|---|
| committer | Mehak Mahajan <mmahajan@nicira.com> | 2012-06-26 12:30:26 -0700 |
| commit | 4550b6475456b7b2e44ab464434f03aacdb9f33d (patch) | |
| tree | 03dc6d679227e29170ec6ce787bb051ed3c92227 /DESIGN | |
| parent | 42531d06c2b6d08c570611c6634b8d0d427c82f0 (diff) | |
| download | openvswitch-4550b6475456b7b2e44ab464434f03aacdb9f33d.tar.gz | |
Setting miss_send_len on receiving NXT_SET_ASYNC_CONFIG message.
For the service controllers to receive any asynchronous messages, the
miss_send_len must be set to a non-zero value (refer to DESIGN). On
receiving the NXT_SET_ASYNC_CONFIG message, the miss_send_len is set
to the default value unless it is set to a non-zero value earlier by
the OFPT_SET_CONFIG message.
Signed-off-by: Mehak Mahajan <mmahajan@nicira.com>
Diffstat (limited to 'DESIGN')
| -rw-r--r-- | DESIGN | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -17,8 +17,14 @@ given controller receives OpenFlow asynchronous messages. This section describes how all of these features interact. First, a service controller never receives any asynchronous messages -unless it explicitly configures a miss_send_len greater than zero with -an OFPT_SET_CONFIG message. +unless it changes its miss_send_len from the service controller +default of zero in one of the following ways: + + - Sending an OFPT_SET_CONFIG message with nonzero miss_send_len. + + - Sending any NXT_SET_ASYNC_CONFIG message: as a side effect, this + message changes the miss_send_len to + OFP_DEFAULT_MISS_SEND_LEN (128) for service controllers. Second, OFPT_FLOW_REMOVED and NXT_FLOW_REMOVED messages are generated only if the flow that was removed had the OFPFF_SEND_FLOW_REM flag |