From nobody Tue Jul 30 14:30:24 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WYHhG4PMlz5S4S4 for ; Tue, 30 Jul 2024 14:30:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WYHhG1JFRz51NL for ; Tue, 30 Jul 2024 14:30:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x534.google.com with SMTP id 41be03b00d2f7-7a0c6ab3354so2996731a12.0 for ; Tue, 30 Jul 2024 07:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1722349836; x=1722954636; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JV3kqzLYQbxYKb+83eqR86BmjV+UB45HQ9SlSAvGeo4=; b=ZX7x1w87H+zq8MoRHUhpcfU4NVe+uKkiV5V2cvLDZEj6XwRWZAPlvJeg5d5z8Dtu6k KceEcKOGlhbcav1x+dblt9CiAxZdLYM1QzDgjLXLwmEveHh8vqMNiQozOLTHA2dpe3dE AkQr9Z1t6gxPx8w1xfe8CQiw/1z4grMBL7E8jbGMHOxA7tmAdP5umsqjca3n9gN6QXRz 1ygRqMPFDUv6IMPoXvnASm6ip3Yq5lzMtVfn6MONH75N8uXrEaeq0DYU2uo/Cb/tI90O ecIgQeTJLxFbpR9Mokdo7bQ5CaDGtWRUr38sJnCnSMYDVy+EgSC2stkUSQglUvDQdawM Ye0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722349836; x=1722954636; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JV3kqzLYQbxYKb+83eqR86BmjV+UB45HQ9SlSAvGeo4=; b=jFXl/hDUpD9T3EA0ZYPFgdwJE+d+jmfYxRNvGWIdZDh6yhf6NlqFdR1I+DdXzxJG31 EyZ8irkevor9+Ryrj3wkZMwKuWqktxXtDSScEtlhinwc93FWGBcN0EQzx1v5b077CCek Wc+putV+cSC8938wgs9DNU2P/+9Ers1GFsLfDNS18YJ2kIoKkVK5kV14zUq3ukhYAdqf 5aBuWeM8zgYl4ocaD93uTtmjr35Rmnf6XbXs93TGlZYTI7PY9daJztthor4YqTDaCFHr pz8M2Ehlo8uWGwqBYuV8EhaVEsCo7mi5+U9OLdMLlDlnjqPf9p/8sm+NnKOD8ovXMOMr QMqQ== X-Forwarded-Encrypted: i=1; AJvYcCXQa3jtEcXyoStNI74IqxE80LSa4GaPqKG5wxGV66tiQgwLvxs3YBWLvaPLwOmKszTBnV4sB3OwZ20F2dk9H3IV/NqkkrsZQ0q0ivE= X-Gm-Message-State: AOJu0Yz8I2US1VobQihn1pNrdlPRc+2fpnFVES8Xdvk8Sgok+QIX8bzM Jg5CLgNbXHc0IperXOvedMHLutmL344Et45IQVrTOsZumTiLr0e6dcOMZqaoOg6K1bQm2AjHVfF F1vNhbhQ3l0PvIwuYc6rfecqoQhmxmmN67Foq6Q== X-Google-Smtp-Source: AGHT+IEYamOqWk/JwCb5A+4IJPA7Q3UcyVY60rovbtNaXfzPnLtTLMaVXlq+EU/lVlpIHkqMuVK6gP2T61pQ8JCABNo= X-Received: by 2002:a17:90a:a60c:b0:2c9:6b02:15ca with SMTP id 98e67ed59e1d1-2cf7e879c76mr9801116a91.39.1722349836306; Tue, 30 Jul 2024 07:30:36 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <20240727170122.675f6bfe@ernst.home> <865xsn6ya9.fsf@ltc.des.dev> In-Reply-To: From: Warner Losh Date: Tue, 30 Jul 2024 08:30:24 -0600 Message-ID: Subject: Re: filemon To: Miroslav Lachman <000.fbsd@quip.cz> Cc: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000002c2503061e77d2d7" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WYHhG1JFRz51NL --0000000000002c2503061e77d2d7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jul 30, 2024, 3:39=E2=80=AFAM Miroslav Lachman <000.fbsd@quip.cz> w= rote: > On 30/07/2024 11:10, Dag-Erling Sm=C3=B8rgrav wrote: > > Gary Jennejohn writes: > > [..] > > >> I also load it from /boot/loader.conf using filemon_load=3D"YES" > > > > This does cause the module to be loaded at boot time, but it's slower > > than loading it later, and it increases memory fragmentation. A better > > option is to include "filemon" in the kld_list variable in /etc/rc.conf > > or /etc/rc.conf.d/kld. For instance, > > > > % cat /etc/rc.conf.d/kld/filemon > > kld_list=3D"${kld_list} filemon" > > 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, and that the preferred way is to load > everything from loader.conf. So I'm curious, what's the right thing to > do then? (I load most of my modules from rc.conf) > Either or for filemon. Either rc.conf's kld_list or loader.conf's filemon_load=3DYES. I've been recommending loader.conf since there's slight= ly less memory fragmentation, but even that effect is small. Only drm kmod has to be in kld_list. The performance advantage of the former is no longer there (for UEFI systems) or is very hard to measure on all but super fringe machines (for BIOS). Net booting would favor kld_list though. Warner Kind regards > Miroslav Lachman > > > > --0000000000002c2503061e77d2d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Jul 30, 2024, 3:39=E2=80=AFAM Miroslav Lachman= <000.fbsd@quip.cz> wrote:
On 30/07/2024 11:10, Dag-Erling Sm=C3= =B8rgrav wrote:
> Gary Jennejohn <garyj@gmx.de> writes:

[..]

>> I also load it from /boot/loader.conf using filemon_load=3D"Y= ES"
>
> This does cause the module to be loaded at boot time, but it's slo= wer
> than loading it later, and it increases memory fragmentation.=C2=A0 A = better
> option is to include "filemon" in the kld_list variable in /= etc/rc.conf
> or /etc/rc.conf.d/kld.=C2=A0 For instance,
>
>=C2=A0 =C2=A0 =C2=A0 % cat /etc/rc.conf.d/kld/filemon
>=C2=A0 =C2=A0 =C2=A0 kld_list=3D"${kld_list} filemon"

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, and that the preferred way is to load
everything from loader.conf. So I'm curious, what's the right thing= to
do then? (I load most of my modules from rc.conf)

Either or for filemon. Eit= her rc.conf's kld_list or loader.conf's filemon_load=3DYES. I'v= e been recommending loader.conf since there's slightly less memory frag= mentation, but even that effect is small. Only drm kmod has to be in kld_li= st.

The performance adva= ntage of the former is no longer there (for UEFI systems) or is very hard t= o measure on all but super fringe machines (for BIOS). Net booting would fa= vor kld_list though.

War= ner

Kind regards
Miroslav Lachman



--0000000000002c2503061e77d2d7--