Messages in this thread | | | Date | Mon, 22 Mar 2004 14:51:36 -0800 | From | Mike Fedyk <> | Subject | Re: Bloat report 2.6.3 -> 2.6.4 |
| |
Matt Mackall wrote: > On Sun, Mar 14, 2004 at 01:32:20AM +0100, Adrian Bunk wrote: > >>On Sat, Mar 13, 2004 at 05:59:40PM -0600, Matt Mackall wrote: >> >>>On Sat, Mar 13, 2004 at 06:57:13PM +0100, Adrian Bunk wrote: >>>... >>> >>>>>But I think it's fair to say that new features that are on by default >>>>>are in fact bloat in some sense. >>>> >>>>Perhaps in some sense, but not in any interesting sense. >>>> >>>>For the average computer you can buy at your supermarket today it isn't >>>>very interesting whether the kernel is bigger by 1 MB or not. >>>> >>>>People who need to care about the size of the kernel [1] use hand-tuned >>>>.config's that are far away from defconfig - and those people wouldn't >>>>enable unneeded features that are on by default. >>> >>>And my coverage of creep in other _commonly used_ parts of the kernel >>>would then be nil. Given that allyesconfig can't be expected to build >>>a kernel on any given day, defconfig is the least arbitrary and most >>>useful of arbitrary choices. >>> >>> >>>>You use a metric "size increase of a defconfig kernel [2]", and I simply >>>>claim that this metric doesn't measure anything useful for practical >>>>purposes. >>> >>>defconfig is not an unreasonable approximation of features people use. >> >>What exactly is your goal? >> >>As already said: >> *** For the average user, the size of the kernel doesn't matter *** [1] >> *** People that care about size don't use defconfig *** > > > Neither of these things matter. The important thing is that defconfig > encompasses a range of common options that are likely to be used, thus > people care about growth in those areas regardless of what subset or > superset they actually use. It is not possible to see growth in the > code for option FOO if option FOO is not enabled. As I pointed out in > the last message, allyesconfig would be ideal for my purposes and > fails both of the above quite dramatically.
With CONFIG_BROKEN, in the kernel for a while, why doesn't allyesconfig work on a stock kernel? Maybe there are some logic errors in kconfig... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |