On 6/29/23 16:08, Simon Horman wrote:
> On Sun, Jun 11, 2023 at 06:58:26PM +0300, Eli Britstein via dev wrote:
>> Vport's offloads are done on the tracked orig-in-port, but the flow itself
>> is associated in the vport's map.
>>
>> Removing the physdev will flush all the ports that are on its map,
On Sun, Jun 11, 2023 at 06:58:26PM +0300, Eli Britstein via dev wrote:
> Vport's offloads are done on the tracked orig-in-port, but the flow itself
> is associated in the vport's map.
>
> Removing the physdev will flush all the ports that are on its map, but
> not the ones on other netdevs' maps.
Vport's offloads are done on the tracked orig-in-port, but the flow itself
is associated in the vport's map.
Removing the physdev will flush all the ports that are on its map, but
not the ones on other netdevs' maps. Since flows take reference count on
both their vport and their physdev, the
