[ovs-dev] [PATCH v3] ofproto: Implement OF1.4 error code for set-async-config

Ben Pfaff blp at ovn.org
Mon Nov 30 04:39:20 UTC 2015


The field we are discussing is a bit-mask.  Only the bits with indexes 3
and 4 may be set, but why is it a problem if no bits are set?

On Mon, Nov 30, 2015 at 09:55:36AM +0530, Ambika Arora wrote:
> Hi Ben,
> 
> As per OF1.4 specification section 7.4.5, the value for enum
> ofp_table_reason with reasons OFPTR_VACANCY_DOWN =3 and OFPTR_VACANCY_UP=4.
> So, the controller can't set the value to 0.
> 
> With Regards,
> Ambika Arora
> 
> 
> On Mon, Nov 30, 2015 at 7:11 AM, Ben Pfaff <blp at ovn.org> wrote:
> 
> > On Tue, Nov 24, 2015 at 05:40:19PM +0530, Ambika Arora wrote:
> > > This patch adds support for Openflow1.4 error codes for set-async-config.
> > > In this patch, a new error type, OFPET_ASYNC_CONFIG_FAILED is introduced
> > > that enables the switch to properly inform the controller when controller
> > > tries to set invalid mask or unsupported configuration.
> > >
> > > Signed-off-by: Ambika Arora <ambika.arora at tcs.com>
> > > ---
> > > 1. Implemented review comments.
> > > 2. Rebased with latest master.
> >
> > Why does table status have a minimum value?  That is, why can't a
> > controller set it to 0?
> >



More information about the dev mailing list