On Wed, Apr 3, 2019 at 7:19 AM Roi Dayan wrote:
>
>
>
> On 02/04/2019 20:14, John Hurley wrote:
> > On Tue, Apr 2, 2019 at 4:05 PM Roi Dayan wrote:
> >>
> >>
> >>
> >> On 02/04/2019 12:27, John Hurley wrote:
> >>> The TC datapath only permits the offload of mirr actions if they are
> >>> egress.
On 02/04/2019 20:14, John Hurley wrote:
> On Tue, Apr 2, 2019 at 4:05 PM Roi Dayan wrote:
>>
>>
>>
>> On 02/04/2019 12:27, John Hurley wrote:
>>> The TC datapath only permits the offload of mirr actions if they are
>>> egress. To offload TC actions that output to OvS internal ports, ingress
On Tue, Apr 2, 2019 at 4:05 PM Roi Dayan wrote:
>
>
>
> On 02/04/2019 12:27, John Hurley wrote:
> > The TC datapath only permits the offload of mirr actions if they are
> > egress. To offload TC actions that output to OvS internal ports, ingress
> > mirr actions are required. At the TC layer, an
On 02/04/2019 12:27, John Hurley wrote:
> The TC datapath only permits the offload of mirr actions if they are
> egress. To offload TC actions that output to OvS internal ports, ingress
> mirr actions are required. At the TC layer, an ingress mirr action passes
> the packet back into the
The TC datapath only permits the offload of mirr actions if they are
egress. To offload TC actions that output to OvS internal ports, ingress
mirr actions are required. At the TC layer, an ingress mirr action passes
the packet back into the network stack as if it came in the action port
rather
