From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: (remove) event not supported.
Date: Sat, 31 Mar 2001 14:56:28 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98605094922205@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98597321622555@msgid-missing>
> > AFAICT there is no need for another count, you can do
> > MOD_INC_USE_COUNT
> > in any module function. The use count does not have to be for just
> > open. Add MOD_INC_USE_COUNT to the probe() function
> > for each new device.
>
> So what if I want to unload a module for a device that still exists?
> These counts are also used in this way for non-hot-plugged devices.
It's important to have the same policy for MOD_INC_USE_COUNT
in all drivers. Including drivers, like network drivers, where the use
count updating is automated ... both for hotpluggable drivers, and for
the other kind.
> For PCMCIA, device counts for each driver are published in
> /proc/bus/pccard/drivers, and cardmgr uses this information to help
> decide when to unload drivers.
I suppose USB could add a third field to /proc/bus/usb/drivers;
and PCI could add a /proc/bus/pci/drivers file too. It'd work.
Maybe those could be argued as 2.4 features; but going that way
doesn't seem like the right general direction. It's clearly a generic
facility that all hotpluggable drivers need, which in my book means
it's best to do it only once.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-03-31 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 17:21 (remove) event not supported David Brownell
2001-03-31 1:00 ` Brad Hards
2001-03-31 2:03 ` Keith Owens
2001-03-31 2:12 ` Brad Hards
2001-03-31 3:48 ` David Hinds
2001-03-31 8:55 ` Brad Hards
2001-03-31 14:56 ` David Brownell [this message]
2001-03-31 15:02 ` David Brownell
2001-03-31 15:49 ` Keith Owens
2001-03-31 16:05 ` David Brownell
2001-03-31 16:18 ` Keith Owens
2001-03-31 16:52 ` David Brownell
2001-04-01 3:02 ` David Hinds
2001-04-01 3:03 ` David Hinds
2001-04-01 5:26 ` Douglas Gilbert
2001-04-02 2:56 ` Trond Eivind Glomsrød
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-98605094922205@msgid-missing \
--to=david-b@pacbell.net \
--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).