From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Device count (to be done with)
Date: Tue, 16 Oct 2001 05:37:32 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100321125829686@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100274805227939@msgid-missing>
On Tue, Oct 16, 2001 at 02:03:23PM +1000, Keith Owens wrote:
>
> I am still not convinced that you need a separate count field, if
> _either_ count is non-zero then the module will not be unloaded. A
> single count is all that is required.
I agree, I think the current module count is just fine.
Again, what is the problem that you are trying to solve here?
The fact that when a device is removed, the driver is unloaded?
Is that a good goal? And if so, why? And why can't the current counter
be used for just that reason?
Right now there is a history of only incrementing the module usage
count when a userspace program opens a file through the driver. That
can _easily_ be changed to increment and decrement when the device is
seen, and removed respectively, for hotpluggable devices. The only ones
who will be inconvenienced would be the developers, hence the present
situation :)
thanks,
greg k-h
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-10-16 5:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 20:06 Device count (to be done with) Stamatis Mitrofanis
2001-10-11 15:01 ` Oliver Neukum
2001-10-12 22:53 ` Stamatis Mitrofanis
2001-10-13 8:45 ` Oliver Neukum
2001-10-15 0:15 ` Stamatis Mitrofanis
2001-10-15 9:39 ` Oliver.Neukum
2001-10-15 22:27 ` Stamatis Mitrofanis
2001-10-16 4:03 ` Keith Owens
2001-10-16 5:37 ` Greg KH [this message]
2001-10-16 5:59 ` Keith Owens
2001-10-16 7:02 ` David Brownell
2001-10-16 8:23 ` Oliver Neukum
2001-10-16 8:29 ` Oliver Neukum
2001-10-16 8:47 ` Keith Owens
2001-10-16 12:00 ` Oliver Neukum
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=marc-linux-hotplug-100321125829686@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).