Date: Wed, 31 Jul 2024 19:11:13 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: void <void@f-m.fm> Cc: freebsd-current@freebsd.org Subject: Re: filemon Message-ID: <20240731191113.ec80be6bcba46cf91f59a906@dec.sakura.ne.jp> In-Reply-To: <ZqkEqkzANCev2Rye@int21h> 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> <D9B5CEBB-3AD3-4D0B-AFD5-33CB5EE0207B@riseup.net> <20240730235707.312d5493197351c9f7e8e649@dec.sakura.ne.jp> <ZqkEqkzANCev2Rye@int21h>
index | next in thread | previous in thread | raw e-mail
On Tue, 30 Jul 2024 16:20:10 +0100 void <void@f-m.fm> wrote: > On Tue, Jul 30, 2024 at 11:57:07PM +0900, Tomoaki AOKI wrote: > > >Another aspect is that loading multiple too large modules easily makes > >boots crash. Staging area (memory region which loader allocates to load > >kernel and modules, and maybe configured buffers) is limited. > > This is why I went looking for filemon as kernel device in the manpage initially. > Generally, in the kernel config I'll comment out stuff thats not going to be used > and add stuff i know is needed, instead of using loader.conf or other methods. > -- If so, linking filemon into kernel is a bad idea. Still consumes staging area, as the kernel becomes larger. Would suppress the size of module header, though. Loading modules via /boot/loader.conf[.local] would be better limited with what actually needed to boot (like zfs.ko for Root on ZFS) and expricitly required to do so. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240731191113.ec80be6bcba46cf91f59a906>