Date: Tue, 30 Jul 2024 15:36:17 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: filemon Message-ID: <8d258cc9-8b13-4c62-9fc4-c6babac17187@quip.cz> In-Reply-To: <86sevr5fyj.fsf@ltc.des.dev> References: <ZqT6_a_0F8DCUsBm@int21h> <CAFDf7UKxhSu%2BqMGV1KahrSX9ho8vFut4avxNVX4D8QGa6%2B%2BTjQ@mail.gmail.com> <20240727170122.675f6bfe@ernst.home> <865xsn6ya9.fsf@ltc.des.dev> <a5471d18-7f88-4e24-8518-2c7a67ddd7f1@quip.cz> <86sevr5fyj.fsf@ltc.des.dev>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30/07/2024 12:31, Dag-Erling Smørgrav wrote: > Miroslav Lachman <000.fbsd@quip.cz> writes: >> Dag-Erling Smørgrav <des@FreeBSD.org> writes: >>> This does cause the module to be loaded at boot time, but it's slower >>> than loading it later, and it increases memory fragmentation. >> Does this also apply today? I recently read from someone on a mailing >> list that the kld_list in rc.conf is no longer needed, that any >> problems it used to solve are solved, > > Loader I/O performance is much better these days so loading modules > pre-boot doesn't slow the boot down much any more, but it's still more > than zero, and it still increases low memory fragmentation, and you > still can't unload a module that was loaded pre-boot. > >> and that the preferred way is to load everything from loader.conf. > > I suspect you're extrapolating here. There is a very small number of > cases where loading pre-boot is required (e.g. zfs.ko if your root is on > zfs) or recommended (e.g. USB HID drivers due to probe ordering issues) > but in the majority of cases, it is still better (even if only slightly) > to wait until after boot. Thank you for the explanation. I will continue to use kld_list. Kind regards Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d258cc9-8b13-4c62-9fc4-c6babac17187>