From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Sat, 19 Apr 2003 04:39:09 +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 Andrew Morton wrote: > Steven Dake wrote: > >>A much better solution could be had by select()ing on a filehandle >>indicating when a new hotswap event is ready to be processed. No races, >>no security issues, no performance issues. > > > I must say that I've always felt this to be a better approach than the > /sbin/hotplug callout. Better in some environments, not all. It's a tradeoff. Me, I'd far rather allocate those hotplug resources on demand than pre-allocate them into Yet Another Daemon. For bounded response-time systems, or for systems that are generating huge event streams, I'd likely want more control though. > Apart from the performance issue, it means that the kernel can buffer the > "insertion" events which happen at boot-time discovery until the userspace > handler attaches itself. It could do that regardless of whether the event is eventually delivered through some socket or by spawning a new process. The way hotplug events are handled after some subsystem decides to send them isn't written in stone. They've been asynchronous all through the 2.4 series, so queueing is semantically OK. - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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