Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #58783
| From | Thomas Goirand <zigo@debian.org> |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Re: Generating a cloud / VM kernel package |
| Date | 2017-08-27 16:20 +0200 |
| Message-ID | <uj6zU-mY-11@gated-at.bofh.it> (permalink) |
| References | <uiG2J-81p-3@gated-at.bofh.it> <uiGFr-8ta-11@gated-at.bofh.it> |
| Organization | Debian |
On 08/26/2017 12:15 PM, Martin Zobel-Helas wrote: > a) we need to decide then if we need one kernel flavour for each cloud > provider or if we can agree on a basic set of kernel compile options > that every cloud provider can use. I don't think that's needed at all. > b) most kernels Debian ships are kernels that have most drivers needed > as modules, so even though the kernel images are big, the kernel should > only load modules it really needs. Size is a concern, yes. Having too many modules slows down all sorts of things. I'm not sure, but aren't all modules added to the initrd by default? > Thomas, can you elaborate why you think this a good idea? Is this about > boot time of the kernel image? The thing I really do not want to have is > additional kernel source uploads to the archive for just those cloud > kernel images, but you already considered that a bad idea (from what I > read between your lines). Basically, the only thing that I want to see is a specific config for that kernel, nothing else. Otherwise, it's going to be too much maintenance work. Indeed, it should *not* be a different source upload, that's too much work as well. There also may be some optimization that we could do. Also, I don't see this happening without a prior agreement from the kernel team (which means probably that Ben has to agree). On our side, we could prepare a list of kernel modules that we do *not* want. Cheers, Thomas Goirand (zigo)
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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