[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190415.154551.760186169164643025.davem@davemloft.net>
Date: Mon, 15 Apr 2019 15:45:51 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: simon.horman@...ronome.com
Cc: jakub.kicinski@...ronome.com, netdev@...r.kernel.org,
oss-drivers@...ronome.com, john.hurley@...ronome.com
Subject: Re: [PATCH net-next 00/11] Flower flow merging
From: Simon Horman <simon.horman@...ronome.com>
Date: Mon, 15 Apr 2019 16:55:52 +0200
> John Hurley says,
>
> These patches deal with 'implicit recirculation' on the NFP. This is a
> firmware feature whereby a packet egresses to an 'internal' port meaning
> that it will recirculate back to the header extract phase with the
> 'internal' port now marked as its ingress port. This internal port can
> then be matched on by another rule. This process simulates how OvS
> datapath outputs to an internal port. The FW traces the packet's
> recirculation route and sends a 'merge hint' to the driver telling it
> which flows it matched against. The driver can then decide if these flows
> can be merged to a single rule and offloaded.
>
> The patches deal with the following issues:
>
> - assigning/freeing IDs to/from each of these new internal ports
> - offloading rules that match on internal ports
> - offloading neighbour table entries whose egress port is internal
> - handling fallback traffic with an internal port as ingress
> - using merge hints to create 'faster path' flows and tracking stats etc.
Series applied, thanks Simon.
Powered by blists - more mailing lists