20 messages in org.freebsd.freebsd-arch[RFC] kldunload -f argument. | From | Sent On | Attachments |
|---|---|---|
| Poul-Henning Kamp | Jul 8, 2004 1:21 pm | |
| Brian Fundakowski Feldman | Jul 8, 2004 1:58 pm | |
| Dag-Erling Smørgrav | Jul 8, 2004 1:58 pm | |
| Poul-Henning Kamp | Jul 8, 2004 2:03 pm | |
| Dag-Erling Smørgrav | Jul 8, 2004 2:14 pm | |
| Poul-Henning Kamp | Jul 8, 2004 2:19 pm | |
| Bruce M Simpson | Jul 8, 2004 2:30 pm | |
| Sam Leffler | Jul 8, 2004 2:41 pm | |
| Lukas Ertl | Jul 8, 2004 2:51 pm | |
| Magnus B{ckstr|m | Jul 9, 2004 2:54 am | |
| Brian Somers | Jul 9, 2004 3:37 am | |
| Magnus B{ckstr|m | Jul 9, 2004 3:42 am | |
| Poul-Henning Kamp | Jul 9, 2004 3:42 am | |
| Brian Somers | Jul 9, 2004 4:00 am | |
| Poul-Henning Kamp | Jul 9, 2004 4:11 am | |
| Poul-Henning Kamp | Jul 9, 2004 5:06 am | |
| Robert Watson | Jul 9, 2004 7:32 am | |
| Poul-Henning Kamp | Jul 9, 2004 7:35 am | |
| Pawel Jakub Dawidek | Jul 9, 2004 7:51 am | |
| Paul Schenkeveld | Jul 13, 2004 3:36 am |
| Subject: | [RFC] kldunload -f argument. | |
|---|---|---|
| From: | Poul-Henning Kamp (ph...@phk.freebsd.dk) | |
| Date: | Jul 9, 2004 7:35:56 am | |
| List: | org.freebsd.freebsd-arch | |
In message <Pine...@fledge.watson.org>,
Robert Watson writes:
On Fri, 9 Jul 2004, Brian Somers wrote:
I'm not sure I see any real-world application for this ? Can you give an example ? Why would you load a module and not use it ?
I can't think of any non-development-environment reasons unless there's room for modules being loaded early to be able to make assumptions about their environment at ACTIVATE time (such as a root filesystem being available).
We actually have an example in the form of snd_driver, which forces all the sound modules to load, with the intent that when you unload, the attached ones are left running. We also have a lot of functionality compiled into GENERIC that many people don't use or use only infrequently -- when that functionality is compiled into modules, we frequently automatically load modules during a file system mount, netgraph pieces, etc. When they're no longer in use, they hang around. In a world where we consistently load modules on demand, and those modules remain idle after use, it would be somewhat nice to be able to simply say "Ok, modules no longer needed, please unload yourselves".
Yes, but I found out why this is troublesome: Modules != KLD.
One KLD may contain multiple modules.
I think that if we need activate/quiesce on a per module interface then we should not do it with KLD granularity.
-- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 ph...@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.