[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43abab53-1425-0bff-9f79-50bd47567605@gmail.com>
Date: Tue, 29 Oct 2019 16:14:53 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Matteo Croce <mcroce@...hat.com>,
Eric Dumazet <eric.dumazet@...il.com>
Cc: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
netdev <netdev@...r.kernel.org>,
Jay Vosburgh <j.vosburgh@...il.com>,
Veaceslav Falico <vfalico@...il.com>,
Andy Gospodarek <andy@...yhouse.net>,
"David S . Miller" <davem@...emloft.net>,
Stanislav Fomichev <sdf@...gle.com>,
Daniel Borkmann <daniel@...earbox.net>,
Song Liu <songliubraving@...com>,
Alexei Starovoitov <ast@...nel.org>,
Paul Blakey <paulb@...lanox.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v2 4/4] bonding: balance ICMP echoes in layer3+4
mode
On 10/29/19 4:03 PM, Matteo Croce wrote:
> Hi Eric,
>
> this would work for locally generated echoes, but what about forwarded packets?
> The point behind my changeset is to provide consistent results within
> a session by using the same path for request and response,
> but avoid all sessions flowing to the same path.
> This should resemble what happens with TCP and UDP: different
> connections, different port, probably a different path. And by doing
> this in the flow dissector, other applications could benefit it.
In principle it is fine, but I was not sure of overall impact of your change
on performance for 99.9% of packets that are not ICMP :)
Powered by blists - more mailing lists