Currently, if a flow reply results in a message which exceeds
the maximum reply size, it will assert OVS. This would happen
when OVN uses OpenFlow15 to add large flows, and they get read
using OpenFlow10 with ovs-ofctl.
This patch prevents this and adds a test case to make sure the
code behaves as
Hi Eelco,
On 1/5/22 10:48, Eelco Chaudron wrote:
Currently, if a flow reply results in a message which exceeds
the maximum reply size, it will assert OVS. This would happen
when OVN uses OpenFlow15 to add large flows, and they get read
using OpenFlow10 with ovs-ofctl.
This patch prevents this a
On 7 Jan 2022, at 13:34, Maxime Coquelin wrote:
> Hi Eelco,
>
> On 1/5/22 10:48, Eelco Chaudron wrote:
>> Currently, if a flow reply results in a message which exceeds
>> the maximum reply size, it will assert OVS. This would happen
>> when OVN uses OpenFlow15 to add large flows, and they get r
On 1/7/22 13:43, Eelco Chaudron wrote:
>
>
> On 7 Jan 2022, at 13:34, Maxime Coquelin wrote:
>
>> Hi Eelco,
>>
>> On 1/5/22 10:48, Eelco Chaudron wrote:
>>> Currently, if a flow reply results in a message which exceeds
>>> the maximum reply size, it will assert OVS. This would happen
>>> when OV
On 7 Jan 2022, at 14:15, Ilya Maximets wrote:
> On 1/7/22 13:43, Eelco Chaudron wrote:
>>
>>
>> On 7 Jan 2022, at 13:34, Maxime Coquelin wrote:
>>
>>> Hi Eelco,
>>>
>>> On 1/5/22 10:48, Eelco Chaudron wrote:
Currently, if a flow reply results in a message which exceeds
the maximum rep