Jarno and I just talked and agreed that it's probably finally time to introduce some capabilities attributes. This would allow us to avoid probing altogether and therefore avoid the logging issues.
On Fri, Apr 25, 2014 at 11:59 AM, Andy Zhou <az...@nicira.com> wrote: > How about we skip logging each unexpected key attributes once? We can > use a u64 bit fields to keep track the flow key attributes in the > kernel module. > > On Thu, Apr 24, 2014 at 6:30 PM, Jesse Gross <je...@nicira.com> wrote: >> On Thu, Apr 24, 2014 at 4:30 PM, Jarno Rajahalme <jrajaha...@nicira.com> >> wrote: >>> >>> On Apr 24, 2014, at 3:32 PM, Ben Pfaff <b...@nicira.com> wrote: >>> >>>> On Thu, Apr 24, 2014 at 02:57:28PM -0700, Jesse Gross wrote: >>>>> I suppose the other possibility is to pass some kind of flag attribute >>>>> with messages indicating that this is a test probe and would silence >>>>> logging. Existing kernels would ignore this so they would still log >>>>> but the behavior would be otherwise unchanged. >>>> >>>> That makes me nervous--it poses the temptation of changing behavior in >>>> some other way, not just log-wise. >>> >>> How about a specific netlink (DP) command to set the logging level and >>> invoking it before and after probing? >> >> I guess something seems vaguely wrong about this to me - it seems to >> assume too much about the kernel implementation. >> _______________________________________________ >> dev mailing list >> dev@openvswitch.org >> http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
