From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kaos@ocs.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: modules and 2.5
Date: Sat, 07 Jul 2001 10:12:28 -0400 [thread overview]
Message-ID: <3B4718CC.483CE54E@mandrakesoft.com> (raw)
In-Reply-To: <m15ISwa-000CGGC@localhost>
Rusty Russell wrote:
>
> In message <3B415489.77425364@mandrakesoft.com> you write:
> > A couple things that would be nice for 2.5 is
> > - let MOD_INC_USE_COUNT work even when module is built into kernel, and
> > - let THIS_MODULE exist and be valid even when module is built into
> > kernel
>
> Hi Jeff,
>
> What use are module use counts, if not used to prevent unloading?
IMHO you should be free to bump the module reference count up and down
as you wish, and be able to read the module reference count.
If you make that assumption, then it becomes possible to use the module
ref count as an internal reference counter, for device opens or
something like that.
In i810_rng.c it eliminated the need for an additional reference
count... until I attempted to compile it into the kernel instead of as a
module, for the first time :)
Jeff
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
next prev parent reply other threads:[~2001-07-07 14:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 5:13 RFC: modules and 2.5 Jeff Garzik
2001-07-03 6:50 ` Sean Hunter
2001-07-03 7:05 ` Jeff Garzik
2001-07-03 7:16 ` Keith Owens
2001-07-03 7:24 ` Jeff Garzik
2001-07-03 7:39 ` Keith Owens
2001-07-03 7:44 ` Jeff Garzik
2001-07-03 7:48 ` Fang Han
2001-07-03 7:18 ` Keith Owens
2001-07-03 12:15 ` jlnance
2001-07-06 10:34 ` Rusty Russell
2001-07-07 14:12 ` Jeff Garzik [this message]
2001-07-08 7:40 ` Rusty Russell
2001-07-11 22:04 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 17:35 Andrzej Krzysztofowicz
2001-07-03 17:39 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B4718CC.483CE54E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox