On 3/13/26 10:38 PM, Ilya Maximets wrote: > Current output of ofproto/detrace doesn't provide information on what > bridge the rules and groups belong to. This may be confusing in > setups with multiple bridges, especially when packets are resubmitted > multiple times through different patch ports. > > Translation cache does have the bridge information though as every > time we lookup the rule we add the XC_TABLE entry that has the bridge > information. We also know when the rule lookup was executed but > didn't result in a match. We can report that as well, so it's easier > to follow the resubmits. Group entries also have a link to ofproto > with the bridge name. > > Note: On a miss, the packet hits the internal drop rule in table 254. > By reporting the fact that there was no match it's easier to > understand why that internal rule is getting hit. > > There is no extra overhead for providing the bridge information as the > data is already there, we just need to print it out. Retis, that is > collecting the detrace output, should also be able to take advantage > of this enhancement. > > Signed-off-by: Ilya Maximets <[email protected]> > --- > > Version 2: > * Fixed missing bridge name for groups. [Adrian]
The system test failure in CI is legit. Need to use OF1.3 for the flow updates, otherwise there is a race when revalidators create an action to send unmatched packets to ovs-ofctl while it is still attached. This is a default behavior for earlier OF versions, 1.3+ has a default drop. I'll send a new version a bit later. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
