From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] rxrpc: ACK handling fixes
Date: Fri, 17 Nov 2023 03:00:23 +0000 [thread overview]
Message-ID: <170019002353.1895.8952802465707802348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231116131259.103513-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 16 Nov 2023 13:12:57 +0000 you wrote:
> Here are a couple of patches to fix ACK handling in AF_RXRPC:
>
> (1) Allow RTT determination to use an ACK of any type as the response from
> which to calculate RTT, provided ack.serial matches the serial number
> of the outgoing packet.
>
> (2) Defer the response to a PING ACK packet (or any ACK with the
> REQUEST_ACK flag set) until after we've parsed the packet so that we
> carry up to date information if the Tx or Rx rings are advanced.
>
> [...]
Here is the summary with links:
- [net,1/2] rxrpc: Fix RTT determination to use any ACK as a source
https://git.kernel.org/netdev/net/c/3798680f2fbb
- [net,2/2] rxrpc: Defer the response to a PING ACK until we've parsed it
https://git.kernel.org/netdev/net/c/1a01319feef7
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-11-17 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 13:12 David Howells
2023-11-16 13:12 ` [PATCH net 1/2] rxrpc: Fix RTT determination to use any ACK as a source David Howells
2023-11-17 6:02 ` Jeffrey E Altman
2023-11-16 13:12 ` [PATCH net 2/2] rxrpc: Defer the response to a PING ACK until we've parsed it David Howells
2023-11-17 6:04 ` Jeffrey E Altman
2023-11-17 3:00 ` 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=170019002353.1895.8952802465707802348.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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
all inboxes | Powered by JetHome®