Adding ctx->xout->slow |= SLOW_CONTROLLER; to xlate_select_group() resolved my issue. Thank you *very* much.
So, does this statement completely shut off caching? How does it work under the hood? I am curious because intuitively "SLOW_CONTROLLER" would mean more caching should be performed at the switch (as the connection with the controller is slow). However, it seems to be working in the opposite way. Any insight into this would be really appreciated. Thanks!! > Date: Tue, 18 Feb 2014 09:37:21 -0800 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: [ovs-dev] xlate_select_group() not being invoked for every packet > > You can add > ctx->xout->slow |= SLOW_CONTROLLER; > to xlate_select_group(). > > On Tue, Feb 18, 2014 at 09:46:03AM -0700, Mohammad Ali Salahuddin wrote: > > Is there a way to turn off this caching? > > Thanks! > > > > > Date: Tue, 18 Feb 2014 08:32:54 -0800 > > > Subject: Re: xlate_select_group() not being invoked for every packet > > > From: [email protected] > > > To: [email protected] > > > CC: [email protected] > > > > > > On Tue, Feb 18, 2014 at 7:31 AM, Mohammad Ali Salahuddin > > > <[email protected]> wrote: > > > > Then, I started to a log a message whenever this function was invoked. > > > > To my > > > > surprise, the logging revealed that this function is not being invoked > > > > for > > > > every packet. > > > > > > > > Is this the expected behavior? Am I missing something? > > > > > > Open vSwitch caches forwarding choices for performance. > > > > > _______________________________________________ > > dev mailing list > > [email protected] > > http://openvswitch.org/mailman/listinfo/dev >
_______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
