linux-kernel - Re: [RFC PATCH 0/6] module, kbuild: Faster boot with custom kernel.

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:	Thu, 19 Feb 2009 12:41:02 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Andreas Robinson <andr345@...il.com>, sam@...nborg.org,
	linux-kernel@...r.kernel.org, Jon Masters <jonathan@...masters.org>
Subject: Re: [RFC PATCH 0/6] module, kbuild: Faster boot with custom kernel.

On Thu, Feb 19, 2009 at 12:15, Rusty Russell <rusty@...tcorp.com.au> wrote:
> On Thursday 19 February 2009 00:27:58 Kay Sievers wrote:
>> some modules wait for 200-500 milliseconds to
>> get the lock released, some larger modules spend 50 milliseconds in
>> load_module(), many of them around 20 milliseconds.
>
> OK, this is an untested hack (don't try unloading modules, not sure symbol
> resolution isn't racy now I've killed the lock).  Does it change the numbers?

That changes it dramatically. The numbers from the sycall until the
linked-in module are now down to 15-25 milliseconds, and for a few
large modules 50-100.

(One crazy exception is ipv6, which takes 620 milliseconds to link, no
idea what it needs to do.)

I'll compare a few bootup times with and without the patch, and come
back later today with the real numbers.

Thanks a lot,
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/