From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 14 Aug 2005 18:52:26 +0000 Subject: Re: udevstart compiled rules Message-Id: <20050814185226.GA15587@vrfy.org> List-Id: References: <20050814062257.GA33928@active.ath.cx> In-Reply-To: <20050814062257.GA33928@active.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sun, Aug 14, 2005 at 09:22:57AM +0300, Amir Shalem wrote: > why does udevstart does not uses compiled rules (created by > udevrulescompile) > when calling udev_rules_init() ? No special reason. udevstart is a single process, that runs once per boot and parses the rules only a single time, so this does not give you a real advantage. I introduced the compiled rules as a _temporary_ hack, cause at SUSE we do hotplug event replay from initramfs after the real root is mounted. Normally there are 600-800 events to be passed to udevd to replay it and every event needed to parse all the rules files again and again. The compiled rules have been a bit faster at bootup time here. In the meantime we moved the rules parsing into the udev daemon which just fork()'s the event without exec() and the parsed rules are still available for the child. This approach looks much better than the precompiled rules, which have never been documented may not stay in its current form. Kay ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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