From: patchwork-bot+netdevbpf@kernel.org
To: David Morley <morleyd.kernel@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
netdev@vger.kernel.org, morleyd@google.com
Subject: Re: [PATCH net-next v3 0/2] tcp: save flowlabel and use for receiver repathing
Date: Tue, 10 Oct 2023 08:30:27 +0000 [thread overview]
Message-ID: <169692662778.15262.2648750491298448747.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231006011841.3558307-1-morleyd.kernel@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 6 Oct 2023 01:18:39 +0000 you wrote:
> From: David Morley <morleyd@google.com>
>
> This patch series stores the last received ipv6 flowlabel. This last
> received flowlabel is then used to help decide whether a packet is
> likely an RTO retransmit or the result of a TLP. This new information
> is used to better inform the flowlabel change decision for data
> receivers.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] tcp: record last received ipv6 flowlabel
https://git.kernel.org/netdev/net-next/c/95b9a87c6a6b
- [net-next,v3,2/2] tcp: change data receiver flowlabel after one dup
https://git.kernel.org/netdev/net-next/c/939463016b7a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-10 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 1:18 [PATCH net-next v3 0/2] tcp: save flowlabel and use for receiver repathing David Morley
2023-10-06 1:18 ` [PATCH net-next v3 1/2] tcp: record last received ipv6 flowlabel David Morley
2023-10-06 1:18 ` [PATCH net-next v3 2/2] tcp: change data receiver flowlabel after one dup David Morley
2023-10-10 8: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=169692662778.15262.2648750491298448747.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=morleyd.kernel@gmail.com \
--cc=morleyd@google.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.