linux-kernel - Re: kbuild: install to a single directory

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:	Mon, 19 Jan 2009 00:24:18 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	Jan Engelhardt <jengelh@...ozas.de>
CC:	sam@...nborg.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kbuild: install to a single directory

Jan Engelhardt wrote:
> Hi,
> 
> This proposed change will collect all kernel modules in the
> single directory, e.g. /lib/modules/2.6.29-rc2/kernel/, without
> any further directory structure. About 475 inodes (with
> almost-allmodconfig) less are used, which should result
> in faster directory traversal (less seeks).

While I agree that current deep-n-wide directory structure is
not very useful.. It still helps in many situations.  For
example, I sometimes need to remember which module name this
particular scsi or network or [s]ata controller needs, and
looking at /lib/modules/$foo/kernel/driver/scsi is usually
sufficient since there isn't many of them in there.  Or,
see (old, compat) -t option to modprobe(8).

In the other words, if to change anything at all, something
in-between is needed instead.  No current deep-n-wide often
single-driver-in-directory structure, and not everything in
one place either.

Maybe add a make variable to tell kbuild to use specified
directory to install modules in this dir to, or to specify
that "this module should go to the parent dir" (eliminates
many driver-in-a-dir cases).

/mjt
--
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/