On Fri, 28 Nov 2014 14:28:31 +0100 "Harald Hoyer" <harald.ho...@gmail.com> wrote:
> > I think what we are seeing here is, that module loading saturates the > udev workers here. So there are at least 16 modprobes (kmod) running > and this hinders further processing of the uevents. > > In theory we could increase arg_children_max before builtin_kmod() > and decrease it again afterwards. > > CC'ing Kay > _______________________________________________ Ok, I've decreased the arg_children_max number from CPU_COUNT * 256 to CPU_COUNT * 64. You where right, it was a bit too much. -- Robert Milasan L3 Support Engineer SUSE Linux (http://www.suse.com) email: rmila...@suse.com GPG fingerprint: B6FE F4A8 0FA3 3040 3402 6FE7 2F64 167C 1909 6D1A _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
