Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mkinitcpio: add missing runtime dependency
Date: Sun, 07 May 2023 06:01:11 +0200	[thread overview]
Message-ID: <20230507040111.4iluXEgLASWyADB2TOmBg4Jwx03tnMSr1qY5SfDyYU8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43778@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/43778#issuecomment-1537282987

Comment:
Yes, sorry; `MODULES_DECOMPRESS=yes` is the (new) default behavior that tries to decompress kernel modules, but setting to `no` (actually anything other than `yes`) will restore the original behavior of copying the modules in as they appear on disk.

Frankly, I don't really see the benefit of decompressing modules. It might trivially improve boot times because critical modules loaded by the initramfs don't need to be decompressed after the initramfs image is loaded, but a) how many modules are people really loading in an initramfs image that the difference is even measurable; and b) it increases the memory footprint of the initramfs, although this is an ephemeral cost.

      parent reply	other threads:[~2023-05-07  4:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07  3:28 [PR PATCH] " kenrap
2023-05-07  3:31 ` classabbyamp
2023-05-07  3:32 ` kenrap
2023-05-07  3:35 ` [PR PATCH] [Closed]: " ahesford
2023-05-07  3:35 ` ahesford
2023-05-07  3:51 ` kenrap
2023-05-07  4:01 ` ahesford [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=20230507040111.4iluXEgLASWyADB2TOmBg4Jwx03tnMSr1qY5SfDyYU8@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).