On 25.11.2019 22:45, Ben Pfaff wrote:
> On Fri, Nov 01, 2019 at 10:24:39PM +0100, Ilya Maximets wrote:
>> Handling of OpenFlow PACKET_OUT implies pushing the packet through
>> the datapath and packet processing inside the datapath could trigger
>> an upcall. In case of system datapath,
On Fri, Nov 01, 2019 at 10:24:39PM +0100, Ilya Maximets wrote:
> Handling of OpenFlow PACKET_OUT implies pushing the packet through
> the datapath and packet processing inside the datapath could trigger
> an upcall. In case of system datapath, 'dpif_execute()' sends packet
> to the kernel module
Hi Ben,
I was not able to reproduce this issue in ovs sandbox, but able to test this
patch on local testbed which had this issue and the patch works.
Thanks & Regards,
Anil Kumar.
-Original Message-
From: Ilya Maximets
Sent: Friday, 22 November, 2019 12:02 AM
To: Ilya Maximets ;
On 01.11.2019 22:24, Ilya Maximets wrote:
> Handling of OpenFlow PACKET_OUT implies pushing the packet through
> the datapath and packet processing inside the datapath could trigger
> an upcall. In case of system datapath, 'dpif_execute()' sends packet
> to the kernel module and returns. If any,
Handling of OpenFlow PACKET_OUT implies pushing the packet through
the datapath and packet processing inside the datapath could trigger
an upcall. In case of system datapath, 'dpif_execute()' sends packet
to the kernel module and returns. If any, upcall will be triggered
inside the kernel and
