Date: Thu, 9 Jul 2020 13:02:23 -0400 From: Mark Johnston <markj@freebsd.org> To: Eugene Grosbein <eugen@grosbein.net> Cc: Michael Tuexen <tuexen@freebsd.org>, freebsd-net@freebsd.org Subject: Re: making SCTP loadable and removing it from GENERIC Message-ID: <20200709170223.GD8947@raichu> In-Reply-To: <1a425cce-4905-1d2f-d5ee-cbeb1c300afc@grosbein.net> References: <20200709151300.GC8947@raichu> <A8BC13AB-F2EC-4819-8920-17395A4DBE64@freebsd.org> <1a425cce-4905-1d2f-d5ee-cbeb1c300afc@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 09, 2020 at 11:36:34PM +0700, Eugene Grosbein wrote: > 09.07.2020 22:41, Michael Tuexen wrote: > > >> I am wondering if anyone has any objections to or concerns about this > >> proposal. Any feedback is appreciated. > > I'm for it. > > > maybe it is acceptable to document user visible changes. This could include > > * parameter tunings in /etc/sysctl.conf are only applied if the SCTP module > > is loaded from /etc/loader.conf. > > You mean /boot/loader.conf. > > This may be relaxed with "sctp_enable" knob for /etc/rc.conf and new startup script > /etc/rc.d/sctp that: a) REQUIRE: kld; b) checks if sctp.ko already loaded and load it as needed; > c) applies sctp sysctl tuning from /etc/sysctl.conf for values that differ. Michael and I talked about this a bit in the past. I propose a more general solution, since it is a problem not just for SCTP: https://reviews.freebsd.org/D25601
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200709170223.GD8947>