On Thu, May 24, 2018 at 6:09 PM, Or Gerlitz <gerlitz...@gmail.com> wrote: > On Thu, May 24, 2018 at 5:22 AM, Jakub Kicinski > <jakub.kicin...@netronome.com> wrote: >> From: John Hurley <john.hur...@netronome.com> >> >> If the egress device of an offloaded rule is a LAG port, then encode the >> output port to the NFP with a LAG identifier and the offloaded group ID. >> >> A prelag action is also offloaded which must be the first action of the >> series (although may appear after other pre-actions - e.g. tunnels). This >> causes the FW to check that it has the necessary information to output to >> the requested LAG port. If it does not, the packet is sent to the kernel >> before any other actions are applied to it. > > Offload decision typically also looks if both devices have the same > switchdev ID. > > In your case, do both reprs gets the same switchdev ID automatically when > being > put into the same team/bond instance? I wasn't sure to see here > changes for that matter
Hi Or, Yes, you are correct. We essentially substituted the switchdev ID check for a repr app check. So an app runs per card and spawns the reprs for that card - each repr has a backpointer to its creating app. When deciding if we can offload a bond, we ensure that all bond ports are reprs and belong to the same app and so same card/switchdev_id.
