[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iLrJiqu1SdjKfkOPcSktvmAUWR2rJWkiPdvzQn+MMAOPg@mail.gmail.com>
Date: Fri, 20 Jun 2025 06:24:23 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Petr Tesarik <ptesarik@...e.com>
Cc: Paolo Abeni <pabeni@...hat.com>, "David S. Miller" <davem@...emloft.net>,
Neal Cardwell <ncardwell@...gle.com>, Kuniyuki Iwashima <kuniyu@...gle.com>,
"open list:NETWORKING [TCP]" <netdev@...r.kernel.org>, David Ahern <dsahern@...nel.org>,
Jakub Kicinski <kuba@...nel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net v2 0/2] tcp_metrics: fix hanlding of route options
On Fri, Jun 20, 2025 at 5:57 AM Petr Tesarik <ptesarik@...e.com> wrote:
>
> I ran into a couple of issues while trying to tweak TCP congestion
> avoidance to analyze a potential performance regression. It turns out
> that overriding the parameters with ip-route(8) does not work as
> expected and appears to be buggy.
Hi Petr
Could you add packetdrill tests as well ?
Given this could accidentally break user setups, maybe net-next would be safer.
Some of us disable tcp_metrics, because metrics used one minute (or
few seconds) in the past are not very helpful, and source of
confusion.
(/proc/sys/net/ipv4/tcp_no_metrics_save set to 1)
Powered by blists - more mailing lists