[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD0BsJWqe-_O6JD=KD7=ktmtFnkA-mo6pnYm2ODtym=JvZyTTw@mail.gmail.com>
Date: Tue, 17 Jun 2025 18:10:47 +0200
From: Maxim Mikityanskiy <maxim@...valent.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Maxim Mikityanskiy <maxtram95@...il.com>, 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
Subject: Re: [PATCH RFC net-next 00/17] BIG TCP for UDP tunnels
On Tue, 17 Jun 2025 at 16:52, Eric Dumazet <edumazet@...gle.com> wrote:
>
> 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 !
I do have a patch. I opened a pull request and pushed it there:
https://github.com/the-tcpdump-group/tcpdump/pull/1329
Powered by blists - more mailing lists