From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
marcelo.leitner@gmail.com, linux-sctp@vger.kernel.org
Subject: Re: [PATCHv2 net-next 00/14] sctp: implement RFC8899: Packetization Layer Path MTU Discovery for SCTP transport
Date: Tue, 22 Jun 2021 18:40:06 +0000 [thread overview]
Message-ID: <162438720650.29926.6241107476929251289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1624384990.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 22 Jun 2021 14:04:46 -0400 you wrote:
> Overview(From RFC8899):
>
> In contrast to PMTUD, Packetization Layer Path MTU Discovery
> (PLPMTUD) [RFC4821] introduces a method that does not rely upon
> reception and validation of PTB messages. It is therefore more
> robust than Classical PMTUD. This has become the recommended
> approach for implementing discovery of the PMTU [BCP145].
>
> [...]
Here is the summary with links:
- [PATCHv2,net-next,01/14] sctp: add pad chunk and its make function and event table
https://git.kernel.org/netdev/net-next/c/745a32117b5a
- [PATCHv2,net-next,02/14] sctp: add probe_interval in sysctl and sock/asoc/transport
https://git.kernel.org/netdev/net-next/c/d1e462a7a5f3
- [PATCHv2,net-next,03/14] sctp: add SCTP_PLPMTUD_PROBE_INTERVAL sockopt for sock/asoc/transport
https://git.kernel.org/netdev/net-next/c/3190b649b4d9
- [PATCHv2,net-next,04/14] sctp: add the constants/variables and states and some APIs for transport
https://git.kernel.org/netdev/net-next/c/d9e2e410ae30
- [PATCHv2,net-next,05/14] sctp: add the probe timer in transport for PLPMTUD
https://git.kernel.org/netdev/net-next/c/92548ec2f1f9
- [PATCHv2,net-next,06/14] sctp: do the basic send and recv for PLPMTUD probe
https://git.kernel.org/netdev/net-next/c/fe59379b9ab7
- [PATCHv2,net-next,07/14] sctp: do state transition when PROBE_COUNT == MAX_PROBES on HB send path
https://git.kernel.org/netdev/net-next/c/1dc68c194571
- [PATCHv2,net-next,08/14] sctp: do state transition when a probe succeeds on HB ACK recv path
https://git.kernel.org/netdev/net-next/c/b87641aff9e7
- [PATCHv2,net-next,09/14] sctp: do state transition when receiving an icmp TOOBIG packet
https://git.kernel.org/netdev/net-next/c/836964083177
- [PATCHv2,net-next,10/14] sctp: enable PLPMTUD when the transport is ready
https://git.kernel.org/netdev/net-next/c/7307e4fa4d29
- [PATCHv2,net-next,11/14] sctp: remove the unessessary hold for idev in sctp_v6_err
https://git.kernel.org/netdev/net-next/c/237a6a2e318c
- [PATCHv2,net-next,12/14] sctp: extract sctp_v6_err_handle function from sctp_v6_err
https://git.kernel.org/netdev/net-next/c/f6549bd37b92
- [PATCHv2,net-next,13/14] sctp: extract sctp_v4_err_handle function from sctp_v4_err
https://git.kernel.org/netdev/net-next/c/d83060759a65
- [PATCHv2,net-next,14/14] sctp: process sctp over udp icmp err on sctp side
https://git.kernel.org/netdev/net-next/c/9e47df005cab
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-06-22 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 18:04 [PATCHv2 net-next 00/14] sctp: implement RFC8899: Packetization Layer Path MTU Discovery for SCTP transport Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 01/14] sctp: add pad chunk and its make function and event table Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 02/14] sctp: add probe_interval in sysctl and sock/asoc/transport Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 03/14] sctp: add SCTP_PLPMTUD_PROBE_INTERVAL sockopt for sock/asoc/transport Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 04/14] sctp: add the constants/variables and states and some APIs for transport Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 05/14] sctp: add the probe timer in transport for PLPMTUD Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 06/14] sctp: do the basic send and recv for PLPMTUD probe Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 07/14] sctp: do state transition when PROBE_COUNT == MAX_PROBES on HB send path Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 08/14] sctp: do state transition when a probe succeeds on HB ACK recv path Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 09/14] sctp: do state transition when receiving an icmp TOOBIG packet Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 10/14] sctp: enable PLPMTUD when the transport is ready Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 11/14] sctp: remove the unessessary hold for idev in sctp_v6_err Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 12/14] sctp: extract sctp_v6_err_handle function from sctp_v6_err Xin Long
2021-06-22 18:04 ` [PATCHv2 net-next 13/14] sctp: extract sctp_v4_err_handle function from sctp_v4_err Xin Long
2021-06-22 18:05 ` [PATCHv2 net-next 14/14] sctp: process sctp over udp icmp err on sctp side Xin Long
2021-06-22 18:40 ` patchwork-bot+netdevbpf [this message]
2021-06-22 22:13 ` [PATCHv2 net-next 00/14] sctp: implement RFC8899: Packetization Layer Path MTU Discovery for SCTP transport David Laight
2021-06-23 1:09 ` Xin Long
2021-06-23 3:48 ` Xin Long
2021-06-23 9:50 ` David Laight
2021-06-23 15:59 ` Xin Long
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=162438720650.29926.6241107476929251289.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.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 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).