On Wed, Aug 19, 2015 at 01:18:37PM +0530, niti Rohilla wrote:
> Thanks Jean.
>
> >Capabilities are not modified by the ofp_table_mod messages,
> >either the implementation is capable, or it is not, and this does not
> >dynamically change. Don't confuse with the 'config' field in
> >ofp_table_desc
Thanks Jean.
>Capabilities are not modified by the ofp_table_mod messages,
>either the implementation is capable, or it is not, and this does not
>dynamically change. Don't confuse with the 'config' field in
>ofp_table_desc that describe if the feature is enabled or not.
>Note that this is one of
On Tue, Aug 18, 2015 at 05:40:34PM +0530, niti Rohilla wrote:
> Hi Jean,
>
> Thanks for your reply. Based on your reply please validate our
> understanding.
>
> 1. From all the commands only OFPTFC_MODIFY needs to be implemented and
> only for a single table in a request. This command is used to
Hi Jean,
Thanks for your reply. Based on your reply please validate our
understanding.
1. From all the commands only OFPTFC_MODIFY needs to be implemented and
only for a single table in a request. This command is used to modify flow
table capabilities and will not modify pipeline processing or an
niti Rohilla wrote :
>
> 2) Page no. 145 of Openflow Specification 1.5.1.
> The command OFPTFC_REPLACE configures the entire pipeline, and the set of
> flow tables in the pipeline must match the set in the request, or an error
> must be returned (see 7.5.4.14). The capability of all flow tables in
Hi,
We are working on implementation of OF1.5 Egress tables (EXT 306). Kindly
answer the following queries:-
1) In OFPMP_TABLE_FEATURES request two new parameters "command" and
"features" are to be introduced. As per the current implementation of table
features in ovs, only empty request body is
