[arch-dev-public] [signoff] udev 118-2

Aaron Griffin aaronmgriffin at gmail.com
Thu Feb 21 17:22:58 EST 2008


On Thu, Feb 21, 2008 at 4:08 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Thu, Feb 21, 2008 at 3:15 PM, Roman Kyrylych
>
> <roman.kyrylych at gmail.com> wrote:
>
>
> > 2008/2/21, Aaron Griffin <aaronmgriffin at gmail.com>:
>  >
>  >
>  > > On Thu, Feb 21, 2008 at 2:26 PM, Pierre Schmitz <pierre at archlinux.de> wrote:
>  >  >  > Am Donnerstag, 21. Februar 2008 08:10:19 schrieb Aaron Griffin:
>  >  >  >
>  >  >  > > Additionally, this package is required for the new initscripts which
>  >  >  >  > are required for the new ISOs. Please sign off
>  >  >  >
>  >  >  >  On my laptop udev needs 20s to load the modules. That's way too much. Was
>  >  >  >  there any change which decreases performance that much?
>  >  >
>  >  >
>  >  > Mine has always been slow. I attempted to improve performance in the
>  >  >  load-modules script, but I believe this is actually a udev issue at
>  >  >  this point... is the change significant from udev 116 and 118? I
>  >  >  noticed little change but I never timed it.
>  >  >
>  >  >  See the new initscripts package which outputs timing stats in ms.
>  >
>  >  See http://bugs.archlinux.org/task/9648
>  >  Users did notice the slowdown too.
>  >  And there is some nice bootchart.
>  >  I guess udev developers did something wrong in 118. *shrugs*
>
>  Oh crapshit.... this is my fault...
>  Ok, throwing this one out to the gallery: Take a look at the new 00
>  rule in the udev package. The point is to export the blacklist to the
>  udev environment for use in load-modules (it should only be computer
>  once). Apparently, that rule is done poorly and it runs for every rule
>  run-through.
>
>  See mod-blacklist here: http://privat.archlinux.dk/bootchart.png
>  That should only be done once instead of the 28902373089434098 times it's run 8)

Idea #1:
   $ cat /etc/udev/rules.d/00-load-blacklist.rules
   ENV{MOD_AUTOLOAD} == "", IMPORT{program} = "/lib/udev/mod-blacklist.sh"

This should only execute it when the env var isn't set. Would someone
mind testing, I won't be home to watch a boot process for a bit




More information about the arch-dev-public mailing list