From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 23 Jan 2004 22:30:48 +0000 Subject: Re: [PATCH] udev - next round of udev event order daemon Message-Id: <20040123223048.GJ23959@kroah.com> List-Id: References: <20040123151425.GA3813@vrfy.org> In-Reply-To: <20040123151425.GA3813@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Jan 23, 2004 at 04:14:25PM +0100, Kay Sievers wrote: > Here is the next round of udevd/udevsend: > > udevsend - If the IPC message we send is not catched by a receiver we fork > the udevd daemon to process this and the following events Problem is we end up forking a lot of udevd instances if the system is under load. That's not good :( I applied this patch, and then added some logic to udevd to only let one instance of it run at a time. It isn't the nicest, but seems to work for now... Hm, sometimes I still loose an event, I think it's back to the udevsend creating too many udevd instances. Care to look at this? Is using ipc calls too messy for this? Others have proposed sockets. Would that make the startup logic simpler? thanks, greg k-h ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ 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