[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89i+ZhT9HWnzjCJepunumS4zLrwGBgGPq6mKiiaa21CKP=g@mail.gmail.com>
Date: Tue, 17 Jun 2025 07:52:39 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Maxim Mikityanskiy <maxtram95@...il.com>
Cc: Daniel Borkmann <daniel@...earbox.net>, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>, David Ahern <dsahern@...nel.org>,
Nikolay Aleksandrov <razor@...ckwall.org>, netdev@...r.kernel.org,
Maxim Mikityanskiy <maxim@...valent.com>
Subject: Re: [PATCH RFC net-next 00/17] BIG TCP for UDP tunnels
On Tue, Jun 17, 2025 at 7:42 AM Maxim Mikityanskiy <maxtram95@...il.com> wrote:
>
> This series consists of two parts that will be submitted separately:
> The only reason why we keep inserting HBH seems to be for the tools that
> parse the packets, but the above drawbacks seem to outweigh this, and
> the tools can be patched (like they need to, in order to be able to
> parse BIG TCP IPv4 now). I have a patch for tcpdump.
This came multiple times.
I want to see the patches coming in the tools, before patches landing in linux.
Having the promise that it can be done is not enough, sorry !
Powered by blists - more mailing lists