Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #58800

Re: Generating a cloud / VM kernel package

From Noah Meyerhans <noahm@debian.org>
Newsgroups linux.debian.kernel
Subject Re: Generating a cloud / VM kernel package
Date 2017-08-28 08:00 +0200
Message-ID <ujlfB-1B9-17@gated-at.bofh.it> (permalink)
References <uiG2J-81p-3@gated-at.bofh.it> <uiGFr-8ta-11@gated-at.bofh.it> <uiLYu-3mY-7@gated-at.bofh.it> <ujftv-6hA-3@gated-at.bofh.it> <ujgfT-6RI-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Mon, Aug 28, 2017 at 01:31:31AM +0100, Ben Hutchings wrote:
> > OTOH, the list of required modules may be small enough for us to
> > enumerate the ones we need for booting in /etc/initramfs-tools/modules.
> 
> ...and then you could use MODULES=list.  initramfs-tools will still
> follow module static dependencies in this case.
> 
> > I will look into this, and we'll see what it does to boot times.
> 
> Note that the saving will mainly be in time to load the initramfs -
> which on Google Compute Engine is done through BIOS disk services that
> have very low performance.  The mere presence of the unneeded modules
> in the initramfs won't cause them to be loaded into the kernel and
> shouldn't make much difference to the time taken to boot after this
> point.

On Amazon's HVM instance families, the initramfs is read from "local"
disk, which may be network-attached or actually local. I haven't
profiled load times in great depth, but my guess is that reading and
uncompressing the image would be the biggest contributors to the load
time. In my experimentation, uncompressing an 18 MB initramfs takes
roughly 500 ms of clock time when read from network storage. That's not
completely insignificant, but considering the fragility of MODULES=list
or MODULES=dep, I'm not sure it's the best place to look for
optimizations right now.

noah

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Generating a cloud / VM kernel package Thomas Goirand <zigo@debian.org> - 2017-08-26 12:00 +0200
  Re: Generating a cloud / VM kernel package Martin Zobel-Helas <zobel@debian.org> - 2017-08-26 12:40 +0200
    Re: Generating a cloud / VM kernel package Ben Hutchings <ben@decadent.org.uk> - 2017-08-26 18:20 +0200
      Re: Generating a cloud / VM kernel package Noah Meyerhans <noahm@debian.org> - 2017-08-28 01:50 +0200
        Re: Generating a cloud / VM kernel package Ben Hutchings <ben@decadent.org.uk> - 2017-08-28 02:40 +0200
          Re: Generating a cloud / VM kernel package Noah Meyerhans <noahm@debian.org> - 2017-08-28 08:00 +0200
    Re: Generating a cloud / VM kernel package Thomas Goirand <zigo@debian.org> - 2017-08-27 16:20 +0200
      Re: Generating a cloud / VM kernel package Noah Meyerhans <noahm@debian.org> - 2017-08-28 16:10 +0200
  Re: Generating a cloud / VM kernel package Ben Hutchings <ben@decadent.org.uk> - 2017-08-26 18:20 +0200
  Re: Generating a cloud / VM kernel package Bastian Blank <waldi@debian.org> - 2017-08-28 14:10 +0200

csiph-web