From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: linux-modules@vger.kernel.org
Subject: Re: [PATCH v2] libkmod: Prefer builtin index over builtin.alias
Date: Sat, 19 Feb 2022 10:41:40 -0800 [thread overview]
Message-ID: <20220219184140.koabdkufdxspccrh@ldmartin-desk2> (raw)
In-Reply-To: <20220219124042.th572glnwdivf2vw@example.org>
On Sat, Feb 19, 2022 at 01:40:42PM +0100, Alexey Gladkov wrote:
>On Mon, Feb 14, 2022 at 11:43:10PM -0800, Lucas De Marchi wrote:
>> On Sun, Feb 13, 2022 at 02:13:39PM +0100, Alexey Gladkov wrote:
>> > On Sat, Feb 12, 2022 at 09:43:35PM -1000, Lucas De Marchi wrote:
>> > > The modules.builtin.alias.bin is way larger than the
>> > > modules.builtin.bin. On a normal "distro kernel":
>> > >
>> > > 21k modules.builtin.alias.bin
>> > > 11k modules.builtin.bin
>> > >
>> > > >From the kernel we get both modules.builtin and modules.builtin.modinfo.
>> > > depmod generates modules.builtin.bin and modules.builtin.alias.bin
>> > > from them respectively. modules.bultin is not going away: it's not
>> > > deprecated by the new index added. So, let's just stop duplicating the
>> > > information inside modules.builtin.alias.bin and just use the other
>> > > index.
>> >
>> > The modules.builtin contains only module names. The modules.builtin.modinfo
>> > contains full info about builtin modules including names.
>> >
>> > I thought that if there is complete information about the modules, then
>> > reading the index with only the names does not make sense. And only in the
>> > absence of modules.builtin.modinfo, you need to fallback to the index
>> > with the names.
>>
>> yeah, but most of the time we really need only the module name, so we
>> can optimize for that. And since we are not getting rid of the other
>> index, we can simply use it first the same way that for modules we first
>> do lookup on lookup modules.dep and only later on modules.aliases.
>
>Yes and no. We can be sure that we don't need aliases. The argument passed
>to utilities can be very similar to the name of a module:
>
>$ modinfo fs-ext4
>name: ext4
>filename: (builtin)
>softdep: pre: crc32c
>license: GPL
>file: fs/ext4/ext4
>description: Fourth Extended Filesystem
>author: Remy Card, Stephen Tweedie, Andrew Morton, Andreas Dilger, Theodore Ts'o and others
>alias: fs-ext4
>alias: ext3
>alias: fs-ext3
>
>By the way, crc32c is also an alias:
>
>$ modinfo crc32c
>filename: /lib/modules/5.14.0.61-centos-alt1.el9/kernel/arch/x86/crypto/crc32c-intel.ko
>alias: crypto-crc32c-intel
>alias: crc32c-intel
>alias: crypto-crc32c
>alias: crc32c
>license: GPL
>description: CRC32c (Castagnoli) optimization using Intel Hardware.
>author: Austin Zhang <austin.zhang@intel.com>, Kent Liu <kent.liu@intel.com>
>rhelversion: 9.0
>srcversion: 1F2B6A533C8243A4017180A
>alias: cpu:type:x86,ven*fam*mod*:feature:*0094*
>depends:
>retpoline: Y
>intree: Y
>name: crc32c_intel
>vermagic: 5.14.0.61-centos-alt1.el9 SMP preempt mod_unload modversions
>
>This is because there are multiple implementations of crc32c. So, information
>about alias of builtin modules is almost always needed.
I was thinking about "optimization" related to libkmod/modprobe (which
is what matters during boot and for the systemd integration). Not for
modinfo which is only called by developers and auxiliary tools.
But then I measured it doing 50k random lookups. The speed up exists but
is under 1% and within the error margin, particularly because we need to
maintain the order doing the alias lookup first. So the main benefit is
really "we are not getting rid of the other index, so could as well just
not duplicate the info".
Another reason for not getting rid of the module is to be able to force
the lookup to be by module name, ignoring the alias. That was the reason
I sent this other series:
https://lore.kernel.org/linux-modules/Yg4DOfCUvIpDDBRd@bombadil.infradead.org/T/#t
so one can get the modinfo from the crc32 module, and not from its
aliases:
$ modinfo --modname crc32
module explicitly:
name: crc32
filename: (builtin)
license: GPL
file: lib/crc32
description: Various CRC32 calculations
author: Matt Domsch <Matt_Domsch@dell.com>
Lucas De Marchi
prev parent reply other threads:[~2022-02-19 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 8:42 [PATCH 1/3] libkmod: Prefer builtin index over builtin.alias Lucas De Marchi
2022-02-11 8:42 ` [PATCH 2/3] depmod: Do not duplicate builtin index Lucas De Marchi
2022-02-11 8:42 ` [PATCH 3/3] depmod: Stop opening modules.modinfo once per module Lucas De Marchi
2022-02-11 10:45 ` [PATCH 1/3] libkmod: Prefer builtin index over builtin.alias Alexey Gladkov
2022-02-12 6:04 ` Lucas De Marchi
2022-02-13 7:43 ` [PATCH v2] " Lucas De Marchi
2022-02-13 13:13 ` Alexey Gladkov
2022-02-15 7:43 ` Lucas De Marchi
2022-02-19 12:40 ` Alexey Gladkov
2022-02-19 18:41 ` Lucas De Marchi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220219184140.koabdkufdxspccrh@ldmartin-desk2 \
--to=lucas.demarchi@intel.com \
--cc=gladkov.alexey@gmail.com \
--cc=linux-modules@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox