On 3/16/22 15:08, Eelco Chaudron wrote:
>
>
> On 14 Jul 2021, at 14:33, Eelco Chaudron wrote:
>
>> On 8 Jul 2021, at 21:21, Ilya Maximets wrote:
>>
>>> On 5/24/21 2:39 PM, Timothy Redaelli wrote:
On Tue, 18 May 2021 06:17:48 -0400
Eelco Chaudron wrote:
> Due to flow lookup
On 14 Jul 2021, at 14:33, Eelco Chaudron wrote:
> On 8 Jul 2021, at 21:21, Ilya Maximets wrote:
>
>> On 5/24/21 2:39 PM, Timothy Redaelli wrote:
>>> On Tue, 18 May 2021 06:17:48 -0400
>>> Eelco Chaudron wrote:
>>>
Due to flow lookup optimizations, especially in the resubmit/clone cases,
On 8 Jul 2021, at 21:21, Ilya Maximets wrote:
> On 5/24/21 2:39 PM, Timothy Redaelli wrote:
>> On Tue, 18 May 2021 06:17:48 -0400
>> Eelco Chaudron wrote:
>>
>>> Due to flow lookup optimizations, especially in the resubmit/clone cases,
>>> we might end up with multiple ct_clear actions, which
On 5/24/21 2:39 PM, Timothy Redaelli wrote:
> On Tue, 18 May 2021 06:17:48 -0400
> Eelco Chaudron wrote:
>
>> Due to flow lookup optimizations, especially in the resubmit/clone cases,
>> we might end up with multiple ct_clear actions, which are not necessary.
>>
>> This patch only adds the
On Tue, 18 May 2021 06:17:48 -0400
Eelco Chaudron wrote:
> Due to flow lookup optimizations, especially in the resubmit/clone cases,
> we might end up with multiple ct_clear actions, which are not necessary.
>
> This patch only adds the ct_clear action to the datapath if any ct state
> is
Due to flow lookup optimizations, especially in the resubmit/clone cases,
we might end up with multiple ct_clear actions, which are not necessary.
This patch only adds the ct_clear action to the datapath if any ct state
is tracked.
Signed-off-by: Eelco Chaudron
---
v2: Insert ct_clear only when
