From: Jakub Kicinski <kuba@kernel.org>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
davem@davemloft.net, linux-sctp@vger.kernel.org,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
timo.voelker@fh-muenster.de
Subject: Re: [PATCH net 2/2] sctp: send pmtu probe only if packet loss in Search Complete state
Date: Tue, 20 Jul 2021 12:50:36 +0200 [thread overview]
Message-ID: <20210720125036.29ed23ba@cakuba> (raw)
In-Reply-To: <b27420c3db63969d3faf00a2e866126dae3b870c.1626713549.git.lucien.xin@gmail.com>
On Mon, 19 Jul 2021 12:53:23 -0400, Xin Long wrote:
> This patch is to introduce last_rtx_chunks into sctp_transport to detect
> if there's any packet retransmission/loss happened by checking against
> asoc's rtx_data_chunks in sctp_transport_pl_send().
>
> If there is, namely, transport->last_rtx_chunks != asoc->rtx_data_chunks,
> the pmtu probe will be sent out. Otherwise, increment the pl.raise_count
> and return when it's in Search Complete state.
>
> With this patch, if in Search Complete state, which is a long period, it
> doesn't need to keep probing the current pmtu unless there's data packet
> loss. This will save quite some traffic.
>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
Can we get a Fixes tag, please?
next prev parent reply other threads:[~2021-07-20 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 16:53 [PATCH net 0/2] sctp: improve the pmtu probe in Search Complete state Xin Long
2021-07-19 16:53 ` [PATCH net 1/2] sctp: improve the code for pmtu probe send and recv update Xin Long
2021-07-19 16:53 ` [PATCH net 2/2] sctp: send pmtu probe only if packet loss in Search Complete state Xin Long
2021-07-20 10:50 ` Jakub Kicinski [this message]
2021-07-20 14:16 ` 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=20210720125036.29ed23ba@cakuba \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=timo.voelker@fh-muenster.de \
/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.