Le Thu, 31 Jul 2008 18:37:57 +0300, Adrian Bunk <bunk@xxxxxxxxxx> a écrit : > I'm just not a fan of adding config options for each few kB of code - > we have to maintain them and the more complex the configuration > becomes the more often it breaks. I'm not a fan of these too, but are there other solutions ? > What became bigger was most likely not related to the patches you > sent. No, it is not. > Where and why did the kernel become bigger? It's not up-to-date with 2.6.26 and 2.6.27-rc1, but Bloatwatch <http://www.selenic.com/bloatwatch/>, by Matt Mackall, is here to answer these questions. I haven't made the analysis for 2.6.26->2.6.27-rc1. > Why did CONFIG_FW_LOADER get enabled? > Due to alnoconfig disabling CONFIG_EMBEDDED? I don't know. Haven't made the analysis for now. > A user will ask: > I'm using $applications with $libraries, can I safely disable this > option? Hard to tell in the general case. > And e.g. according to a quick grep through the sources uClibc's > updwtmp() seems to cease working without flock(). Correct. But on many embedded systems, we don't care about logging past user logins. We might even not care about logins at all. > It costs us maintainance of the option and the #ifdef's and gives > users one way more to shoot themselves into the foot in nontrivial to > detect ways. That's correct, and as I said previously, I fully understand the maintainance problem of all these new configuration options. I must admit that I do not really have more objective technical arguments that would help us deciding whether the code size reduction vs. code maintainance choice should be made in one direction or the other. Sincerly, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
