On Sat, Dec 20, 2014 at 06:40:49PM +0100, Umut Tezduyar Lindskog wrote: > On Sat, Dec 20, 2014 at 6:10 PM, Greg KH <gre...@linuxfoundation.org> wrote: > > On Sat, Dec 20, 2014 at 10:45:34AM +0000, Hoyer, Marko (ADITG/SW2) wrote: > >> Hi, > >> > >> > -----Original Message----- > >> > From: systemd-devel [mailto:systemd-devel- > >> > boun...@lists.freedesktop.org] On Behalf Of Umut Tezduyar Lindskog > >> > Sent: Tuesday, December 16, 2014 4:55 PM > >> > To: systemd-devel@lists.freedesktop.org > >> > Subject: [systemd-devel] Improving module loading > >> > > >> > Hi, > >> > > >> > Is there a reason why systemd-modules-load is loading modules > >> > sequentially? Few things can happen simultaneously like resolving the > >> > symbols etc. Seems like modules_mutex is common on module loads which > >> > gets locked up on few occasions throughout the execution of > >> > sys_init_module. > >> > >> We are actually doing this (in embedded systems which need to be up > >> very fast with limited resources) and gained a lot. Mainly, IO and CPU > >> can be better utilized by loading modules in parallel (one module is > >> loaded while another one probes for hardware or is doing memory > >> initialization). > > > > If you have control over your kernel, why not just build the modules > > into the kernel, then all of this isn't an issue at all and there is no > > overhead of module loading? > > For us, licenses are the problem.
Then you are on your own, and be prepared to deal with the legal issues involved. No sympathy here. greg k-h _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel