-rw------- 1 root root 7.4M Jan 1 22:22 initrd-4.13.12-1-default -rw------- 1 root root 7.5M Mar 9 13:38 initrd-4.14.15-2-default -rw------- 1 root root 7.4M Apr 26 23:08 initrd-4.15.13-2-default -rw------- 1 root root 8.4M Apr 27 00:51 initrd-4.16.3-1-default -rw-r--r-- 1 root root 7.0M Nov 12 13:36 vmlinuz-4.13.12-1-default -rw-r--r-- 1 root root 7.2M Jan 31 21:05 vmlinuz-4.14.15-2-default -rw-r--r-- 1 root root 7.3M Apr 4 22:13 vmlinuz-4.15.13-2-default -rw-r--r-- 1 root root 7.4M Apr 22 15:57 vmlinuz-4.16.3-1-default
I thought I read somewhere in recent weeks to expect kernel package size to shrink in 4.16 or 4.17. Installed size of rpm of 4.16.3 is 106.7% of 4.13.12, so it doesn't seem to have happened yet - if it's ever going to. Obviously whatever I saw wasn't about initrd sizes. What happened to cause the 13.5% jump in initrd size in TW's 4.16?
Hi,
On Fri, Apr 27, 2018 at 9:16 AM Felix Miata mrmazda@earthlink.net wrote:
I thought I read somewhere in recent weeks to expect kernel package size
to
shrink in 4.16 or 4.17.
You might've read about the decrease in lines of code [1], which will not necessarily translate in a decrease in the compiled code. The dropped code was mostly unused CPU architectures which I expect did not have an effect on the i586/x86_64 kernel size.
Robert
[1]: http://lkml.iu.edu/hypermail/linux/kernel/1804.1/06654.html
On 04/27/2018, 08:16 AM, Felix Miata wrote:
What happened to cause the 13.5% jump in initrd size in TW's 4.16?
Better to ask lsinitrd, not us.
-
Felix Miata -
Jiri Slaby -
Robert Munteanu