From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew Morton" Date: Tue, 06 Feb 2001 23:12:32 +0000 Subject: Re: Adding PCMCIA support to the kernel tree -- developers needed. Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org David Brownell wrote: > > When I thought about this last year, my conclusion was that it SHOULD > be OK to have multiple event orderings so long as all were correctly > serialized with respect to essential criteria. Just as if they were database > transactions that didn't interfere with each other. The configuration of a > GNU/Linux operating environment is a transactable problem, and users > have no business caring which hotplug action is handled first ... so long > as each one is handled correctly. Device naming worries me. Suppose we were able to make an entire "hotplug" transaction synchronous and correctly serialised. So when I "insert" my 3c501, the driver load and the open all happen safely and serially. Well, I still want to provide a consistent and predictable ordering of this wrt the "hotplug" of my Acenic card. Why? Because I don't want them to be randomly assigned "eth0" or "eth1" depending on which way the wind is blowing. This means, I think, that we want *global* serialisation of all hotplug activity. *never* do more than one thing at a time. So all driver loads and opens will happen strictly, synchronously in scan order. Nice, simple, and can't be done. _______________________________________________ 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