[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMiNn+k8b0ixYgL2M6X=7WLMM=i1gEoLcdEYkztjsphi=g@mail.gmail.com>
Date: Thu, 24 May 2018 20:09:24 +0300
From: Or Gerlitz <gerlitz.or@...il.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
oss-drivers@...ronome.com, John Hurley <john.hurley@...ronome.com>
Subject: Re: [PATCH net-next 8/8] nfp: flower: compute link aggregation action
On Thu, May 24, 2018 at 5:22 AM, Jakub Kicinski
<jakub.kicinski@...ronome.com> wrote:
> From: John Hurley <john.hurley@...ronome.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
Powered by blists - more mailing lists