lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 17 Feb 2009 12:53:25 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Andreas Robinson <andr345@...il.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>, sam@...nborg.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/6] module, kbuild: Faster boot with custom kernel.

On Tue, Feb 17, 2009 at 11:42, Andreas Robinson <andr345@...il.com> wrote:
> On Mon, Feb 16, 2009 at 11:51 PM, Rusty Russell <rusty@...tcorp.com.au> wrote:
>>
>>  This isn't crazy.  But you'd need to benchmark against the minimal
>> userspace solution: a binary with all the modules built into
>> it which calls sys_init_module on each one, then does the root swizzle
>> or whatever.
>>
>> I think you'd find the difference to be in the noise.

Usual distro setups load like 100+ modules on every bootup. Modprobing
and symbol-resolving is serialized and uses stop_machine(), so there
might be some significant difference here when loading a huge number
of modules individually. Monolithic versus modular kernels usually
make about 2+ seconds difference on a recent laptop.

> your're right and I'll get right on it.

For distros it's probably more interesting not to get rid of the
initramfs, but possibly have the mkinitrd/mkinitramfs tool to pre-link
all the usual modules if faster bootup is expected. Having only the
few modules pre-linked which are usually included in the initramfs,
might, as Rusty expects, not make that much difference.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ