Date: Tue, 9 Apr 2013 11:05:56 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Alfred Perlstein <bright@mu.org>, Amit Rawat <aamitr4@gmail.com> Subject: Re: GSOC 2013 project " Kernel Size Reduction for Embedded System " Message-ID: <CAOjFWZ6ytuKFHYBvrNTMwK8f=_ZDnGY5-naVqscC6YWZ33P8UA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1304091953060.13438@wojtek.tensor.gdynia.pl> References: <CAOhv3dpTM9J9oiLpdw8xOAToXT_tQ3VW4Mv1F%2B8n7xhG%2BJK93w@mail.gmail.com> <alpine.BSF.2.00.1304091935490.13342@wojtek.tensor.gdynia.pl> <516452C7.7040607@mu.org> <alpine.BSF.2.00.1304091953060.13438@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
You have to look at the in-memory sizes, not the on-disk sizes. Linux kernels are very barebones when it comes to what is compiled directly into the kernel image on disk. Everything else is loaded from modules at boot time. Especially if using distro-provided kernels. They even use ram disks / initrds to get around the "can't boot without drivers for Y, but Y is a module and not loaded at boot", adding extra memory pressure that's not shown in the on-disk size of the kernel image file. FreeBSD kernels tend to be the opposite, with everything compiled directly into the kernel image on-disk, and very little actually being loaded via modules. At least GENERIC, anyway. You would need to manually compile kernels with the same sets of drivers on each system, in order to do a proper comparison of on-disk sizes. Or, look at in-memory stats for the two, once the systems are booted, all modules are loaded, and the system is ready for use. Just comparing ls output of default FreeBSD/Linux installs isn't useful in any way. -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ6ytuKFHYBvrNTMwK8f=_ZDnGY5-naVqscC6YWZ33P8UA>