[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iL8Q+11FOBZq-X3kJF-0i5R1zivERQCx-hGHM4CWAFa+w@mail.gmail.com>
Date: Mon, 13 Jan 2025 14:20:14 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Cc: netdev@...r.kernel.org, Simon Horman <horms@...nel.org>,
Neal Cardwell <ncardwell@...gle.com>, Kuniyuki Iwashima <kuniyu@...zon.com>, eric.dumazet@...il.com
Subject: Re: [PATCH net-next 0/2] tcp: add a new PAWS_ACK drop reason
On Fri, Jan 10, 2025 at 3:33 PM Eric Dumazet <edumazet@...gle.com> wrote:
>
> Current TCP_RFC7323_PAWS drop reason is too generic and can
> cause confusion.
>
> One common source for these drops are ACK packets coming too late.
>
> A prior packet with payload already changed tp->rcv_nxt.
>
> Add TCP_RFC7323_PAWS_ACK new drop reason, and do not
> generate a DUPACK for such old ACK.
>
> Eric Dumazet (2):
> tcp: add drop_reason support to tcp_disordered_ack()
> tcp: add TCP_RFC7323_PAWS_ACK drop reason
>
I am sending a V2 :
- Adding one SNMP counter (Neal Cardwell suggestion)
- Fix one typo in changelog
Powered by blists - more mailing lists