netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	dsahern@kernel.org, netdev@vger.kernel.org,
	eric.dumazet@gmail.com, ncardwell@google.com, morleyd@google.com
Subject: Re: [PATCH net] tcp: fix tcp_disordered_ack() vs usec TS resolution
Date: Sat, 09 Dec 2023 01:30:23 +0000	[thread overview]
Message-ID: <170208542364.22393.11705664552724086672.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231207181342.525181-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  7 Dec 2023 18:13:42 +0000 you wrote:
> After commit 939463016b7a ("tcp: change data receiver flowlabel after one dup")
> we noticed an increase of TCPACKSkippedPAWS events.
> 
> Neal Cardwell tracked the issue to tcp_disordered_ack() assumption
> about remote peer TS clock.
> 
> RFC 1323 & 7323 are suggesting the following:
>   "timestamp clock frequency in the range 1 ms to 1 sec per tick
>    between 1ms and 1sec."
> 
> [...]

Here is the summary with links:
  - [net] tcp: fix tcp_disordered_ack() vs usec TS resolution
    https://git.kernel.org/netdev/net/c/9c25aae0132b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-12-09  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 18:13 [PATCH net] tcp: fix tcp_disordered_ack() vs usec TS resolution Eric Dumazet
2023-12-09  1:30 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=170208542364.22393.11705664552724086672.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=morleyd@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).