From: Keith Owens <kaos@ocs.com.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: Unloading drivers, start-up, shut-down and a rewrite (a problem)
Date: Fri, 05 Oct 2001 05:58:58 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100226162806613@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100216891319132@msgid-missing>
On Fri, 05 Oct 2001 01:03:19 +0100,
Stamatis Mitrofanis <ewstam@softhome.net> wrote:
>It's when you have many hotpluggable devices of the same type (handled
>by the same driver). Managing a reference (device) count for each driver
>from the hotpug scripts is necessary for unloading the driver _only_
>after the last such device is unplugged.
That means we are changing the meaning of the module use count on
drivers from "number of devices opened" to "number of devices present
and activated". Not such a bad idea, there has long been a problem
with network drivers that the use count can be zero but the driver code
can be active, rmmod gets very nasty then.
Before I write the code, what needs to change in user space to match
the new semantics? Every device activation and inactivation must
adjust the use count of the supporting module. That is easy for
hotplug but what about PCMCIA and fixed devices? In particular
ifconfig eth0 up must adjust the use count of the module controlling
eth0. A partial solution that only works for hotplug is not a good
idea. Can we get a consistent user space framework for the new
semantics?
_______________________________________________
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-05 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 3:14 Unloading drivers, start-up, shut-down and a rewrite (a problem) Stamatis Mitrofanis
2001-10-04 4:29 ` Keith Owens
2001-10-05 0:03 ` Stamatis Mitrofanis
2001-10-05 5:58 ` Keith Owens [this message]
2001-10-05 6:25 ` David Hinds
2001-10-05 7:13 ` David Brownell
2001-10-05 7:21 ` David Brownell
2001-10-05 7:28 ` Keith Owens
2001-10-05 8:16 ` Oliver Neukum
2001-10-05 8:53 ` David Brownell
2001-10-05 15:26 ` David Hinds
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-100226162806613@msgid-missing \
--to=kaos@ocs.com.au \
--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).