On 9 April 2013 11:47, Edward Tomasz Napierała <tr...@freebsd.org> wrote: > In order to optimize - in this case for size - we need a way to measure > what should we focus on, and it looks like we don't have it yet.
We have a good starting point. We can look at the code/data/bss from each .o file that's included in the build. You can build a bare-bones kernel and modules, and use that to see how big things are. You can group those by subsystem to get an idea of how big each subsystem is. Whether or not it's loaded is (mostly) irrelevant - if we compile out USB but then include it as a module, the underlying size is almost the same anyway. Thanks, Adrian _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
