[systemd-devel] device units rely on udev rules?

Lennart Poettering lennart at poettering.net
Mon May 9 13:08:46 PDT 2011


On Mon, 09.05.11 22:02, Lennart Poettering (lennart at poettering.net) wrote:

> > It's still in the 10 second range on a 600MHz cortex-a8 machine
> > booting from an SD card. I need to dig out my 400MHz arm920t to see
> > how long it takes there. So having udev-less operation in systemd
> > would be nice, even if it's only used on 'embedded'
> 
> Have you checked what precisely takes so long? My guess is that some
> driver has a slow sysfs uevent trigger callback, and that might be
> fixable in the driver. You might want to use strace with timestamps to
> figure out why udev trigger might be so slow.

Also note that only very few devices are exposed and depended on by
systemd. In an embedded env you might be able to simple trigger those
explicitly first, and then trigger the rest afterwards. That way you
don't have to wait 10s, and the triggering will be dispatched in the bg,
but you still get the flexibility that udev can handle hotplugged
devices.

Kay, opinions?

Lennart

-- 
Lennart Poettering - Red Hat, Inc.


More information about the systemd-devel mailing list