From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next] sctp: make the raise timer more simple and accurate
Date: Thu, 25 Nov 2021 18:34:20 -0300 [thread overview]
Message-ID: <YaABXM/RBXaB8fzN@t14s.localdomain> (raw)
In-Reply-To: <edb0e48988ea85997488478b705b11ddc1ba724a.1637781974.git.lucien.xin@gmail.com>
On Wed, Nov 24, 2021 at 02:26:14PM -0500, Xin Long wrote:
> Currently, the probe timer is reused as the raise timer when PLPMTUD is in
> the Search Complete state. raise_count was introduced to count how many
> times the probe timer has timed out. When raise_count reaches to 30, the
> raise timer handler will be triggered.
>
> During the whole processing above, the timer keeps timing out every probe_
> interval. It is a waste for the Search Complete state, as the raise timer
> only needs to time out after 30 * probe_interval.
>
> Since the raise timer and probe timer are never used at the same time, it
> is no need to keep probe timer 'alive' in the Search Complete state. This
> patch to introduce sctp_transport_reset_raise_timer() to start the timer
> as the raise timer when entering the Search Complete state. When entering
> the other states, sctp_transport_reset_probe_timer() will still be called
> to reset the timer to the probe timer.
>
> raise_count can be removed from sctp_transport as no need to count probe
> timer timeout for raise timer timeout. last_rtx_chunks can be removed as
> sctp_transport_reset_probe_timer() can be called in the place where asoc
> rtx_data_chunks is changed.
>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
next prev parent reply other threads:[~2021-11-25 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 19:26 [PATCH net-next] sctp: make the raise timer more simple and accurate Xin Long
2021-11-25 21:34 ` Marcelo Ricardo Leitner [this message]
2021-11-26 5:10 ` patchwork-bot+netdevbpf
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=YaABXM/RBXaB8fzN@t14s.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@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