Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Neal Cardwell <ncardwell@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH net-next 0/2] more accurate DSACK processing for RACK-TLP
Date: Tue, 27 Jul 2021 19:20:05 +0000	[thread overview]
Message-ID: <162741360553.32214.12453870560263718574.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210727144258.946533-1-ncardwell@google.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Tue, 27 Jul 2021 10:42:56 -0400 you wrote:
> This patch series includes two minor improvements to tighten up the accuracy of
> the processing of incoming DSACK information, so that RACK-TLP behavior is
> faster and more precise: first, to ensure we detect packet loss in some extra
> corner cases; and second, to avoid growing the RACK reordering window (and
> delaying fast recovery) in cases where it seems clear we don't need to.
> 
> Neal Cardwell (1):
>   tcp: more accurately check DSACKs to grow RACK reordering window
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] tcp: more accurately detect spurious TLP probes
    https://git.kernel.org/netdev/net-next/c/63f367d9de77
  - [net-next,2/2] tcp: more accurately check DSACKs to grow RACK reordering window
    https://git.kernel.org/netdev/net-next/c/a657db0350bb

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



      parent reply	other threads:[~2021-07-27 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 14:42 Neal Cardwell
2021-07-27 14:42 ` [PATCH net-next 1/2] tcp: more accurately detect spurious TLP probes Neal Cardwell
2021-07-27 14:42 ` [PATCH net-next 2/2] tcp: more accurately check DSACKs to grow RACK reordering window Neal Cardwell
2021-07-27 19:20 ` 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=162741360553.32214.12453870560263718574.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --subject='Re: [PATCH net-next 0/2] more accurate DSACK processing for RACK-TLP' \
    /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

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).