unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: linux-module-builder leads to huge store items
Date: Fri, 11 Sep 2020 16:55:35 +0200	[thread overview]
Message-ID: <87k0x0tlaw.fsf@inria.fr> (raw)
In-Reply-To: <20200911130959.479f9348@scratchpost.org> (Danny Milosavljevic's message of "Fri, 11 Sep 2020 13:09:59 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

>> So, I can think of the following ways to address that:
>> 
>>   1. Remove for example *.c, assuming the out-of-tree modules we package
>>      only care about *.h + build machinery.
>
> The biggest source files, see above, are header files
> (drivers/gpu/drm/amd/include/asic_reg).
>
>>   2. Don’t add all of the Linux source to the store, or at least not
>>      under a new name each time.  One way to do that would be to unpack
>>      the Linux-libre tree within the build tree of the out-of-tree
>>      module.  We’d be reducing GC stress at the expense of a
>>      (reasonable?) increase in module build time.

[...]

> I checked--that would reduce the size of linux-libre-builder by about 800 MB
> (to 255 MB; see [1][2]).
> That would mean that some modules can't be out-of-tree.  But I guess
> that's okay--and we could not-delete some files later if need be.

Yes, that’s OK.  I’d say let’s delete as much as possible, and then, if
it eventually turns out to be a problem for a new out-of-tree module
package, we can re-add files selectively.

Could you give it a try?

> Btw, linux-libre is currently not reproducible--see bug 43301.
> That could introduce a security problem if the Linux kernel and
> an out-of-tree module are compiled differently (they are) and then loaded
> into the same kernel (even now).

One thing at a time.  :-)

Thanks,
Ludo’.


  reply	other threads:[~2020-09-11 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  8:09 linux-module-builder leads to huge store items Ludovic Courtès
2020-09-10 13:04 ` Danny Milosavljevic
2020-09-10 16:26   ` Ludovic Courtès
2020-09-11 11:09     ` Danny Milosavljevic
2020-09-11 14:55       ` Ludovic Courtès [this message]
2020-09-11 17:44         ` Danny Milosavljevic

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0x0tlaw.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).