From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Date: Sat, 12 Apr 2003 08:04:56 +0000 Subject: Re: [ANNOUNCE] udev 0.1 release 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 > Right now, if you plug and then quickly unplug a device, the unplug event > can be handled first. > > It may not happen much in practice, but we have had problem with cardbus > contact bounce causing an event storm in the past. The daemon could just > swallow the first 5 insert/remove pairs and process the final insert only. > > The kernel would have to drop messages on the floor at some point though. That is unavoidable in _any_ scheme. The hotplug spawn scheme wishes to weasle through this by letting kmalloc determine, when to throw away an event. No system can process an infinite amount of events. What's important is an ability to report loss of events and to export a consistent view of devices connected, that can be read at will. Regards Oliver ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ 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