From: Xin Long <lucien.xin@gmail.com>
To: "linux-sctp @ vger . kernel . org" <linux-sctp@vger.kernel.org>,
Michael Tuexen <tuexen@freebsd.org>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Subject: The new sysctl and socket option added for PLPMTUD (RFC8899)
Date: Fri, 11 Jun 2021 16:20:38 -0400 [thread overview]
Message-ID: <CADvbK_c0dmke8Ei2sLiVqZ2ExgcmZyuPwpHBgW9g6Cjdi+rzug@mail.gmail.com> (raw)
Hi, Michael,
In the linux implementation of RFC8899, we decided to introduce one
sysctl and one socket option for users to set up the PLPMUTD probe:
1. sysctl -w net.sctp.plpmtud_probe_interval=1
plpmtud_probe_interval - INTEGER
The interval (in milliseconds) between PLPMTUD probe chunks. These
chunks are sent at the specified interval with a variable size to
probe the mtu of a given path between 2 associations. PLPMTUD will
be disabled when 0 is set.
Default: 0
2. a socket option that can be used per socket, assoc or transport
/* PLPMTUD Probe Interval socket option */
struct sctp_probeinterval {
sctp_assoc_t spi_assoc_id;
struct sockaddr_storage spi_address;
__u32 spi_interval;
};
#define SCTP_PLPMTUD_PROBE_INTERVAL 133
The value above will enable/disable the PLPMUTD probe by setting up the probe
interval for the timer. When it's 0, the timer will also stop and
PLPMUTD is disabled.
By this way, we don't need to introduce more options.
We're expecting to keep consistent with BSD on this, pls check and
share your thoughts.
Thanks.
next reply other threads:[~2021-06-11 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 20:20 Xin Long [this message]
2021-06-11 20:42 ` The new sysctl and socket option added for PLPMTUD (RFC8899) tuexen
2021-06-12 17:32 ` Xin Long
2021-06-12 21:28 ` tuexen
[not found] ` <FEF068AA-C660-4A25-ABFE-D559B1136B58@fh-muenster.de>
2021-07-06 9:12 ` Timo Völker
2021-07-06 16:01 ` Xin Long
2021-07-07 12:36 ` Timo Völker
2021-07-07 16:30 ` Xin Long
2021-07-08 14:18 ` Timo Völker
2021-07-08 15:54 ` Xin Long
2021-07-12 8:09 ` Timo Völker
2021-07-19 16:55 ` 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=CADvbK_c0dmke8Ei2sLiVqZ2ExgcmZyuPwpHBgW9g6Cjdi+rzug@mail.gmail.com \
--to=lucien.xin@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=tuexen@freebsd.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.