On 16.02.24 00:03, Ilya Maximets wrote:
> On 2/15/24 14:23, Simon Horman wrote:
>> On Thu, Feb 15, 2024 at 09:16:38AM +0100, Jakob Meng wrote:
>>> On 30.01.24 10:44, Simon Horman wrote:
On Fri, Jan 26, 2024 at 02:24:51PM +0100, jm...@redhat.com wrote:
> From: Jakob Meng
>
> In a s
On 2/15/24 14:23, Simon Horman wrote:
> On Thu, Feb 15, 2024 at 09:16:38AM +0100, Jakob Meng wrote:
>> On 30.01.24 10:44, Simon Horman wrote:
>>> On Fri, Jan 26, 2024 at 02:24:51PM +0100, jm...@redhat.com wrote:
From: Jakob Meng
In a scenario where OVN does load balancing and then S
On Thu, Feb 15, 2024 at 09:16:38AM +0100, Jakob Meng wrote:
> On 30.01.24 10:44, Simon Horman wrote:
> > On Fri, Jan 26, 2024 at 02:24:51PM +0100, jm...@redhat.com wrote:
> >> From: Jakob Meng
> >>
> >> In a scenario where OVN does load balancing and then SNAT with a OVS
> >> userspace datapath [0
On 30.01.24 10:44, Simon Horman wrote:
> On Fri, Jan 26, 2024 at 02:24:51PM +0100, jm...@redhat.com wrote:
>> From: Jakob Meng
>>
>> In a scenario where OVN does load balancing and then SNAT with a OVS
>> userspace datapath [0], the recirc_depth may be greater than 6. In
>> that case, ovs-vswitchd
On Fri, Jan 26, 2024 at 02:24:51PM +0100, jm...@redhat.com wrote:
> From: Jakob Meng
>
> In a scenario where OVN does load balancing and then SNAT with a OVS
> userspace datapath [0], the recirc_depth may be greater than 6. In
> that case, ovs-vswitchd might drop packets and raise warnings:
>
>
From: Jakob Meng
In a scenario where OVN does load balancing and then SNAT with a OVS
userspace datapath [0], the recirc_depth may be greater than 6. In
that case, ovs-vswitchd might drop packets and raise warnings:
dpif_netdev|WARN|Packet dropped. Max recirculation depth exceeded.
Increasing
