<> System Size Measurement Ikeda (NEC) [translated by ikoma] 1. motivation Want to minmize code size and memory usage. 2. approach Squeezing kernel configs is a key. Investigate the impact of each config item on code size and memory usage. 3. to do Make it clear which has big impact on code size, memory usage. Make it clear which part has inflated between versions. 4. building automatic validation tool The tool is done. * step1 Check that the tool works. * step2 More target versions. We are in this stage now. * step3 More target architectures. -> Information obtained so far has been posted on CELF wiki. 5. Current status Looking the transition data among versions. 6. Result 6.1. step1 Result has been obtained. Some minor issues such that data unavailable for some single config item. 6.2. step2 validating the effect of transition among versions Issues Dependency among config items changes for new version -> Cannot compare! (Cannot compare nearly 30% between 2.6.15 and 2.6.0) Proposed solution Getting a size data for each config, i.e. make it possible to handle single item. Under consideration. 7. Summary Want to discuss a lot, for example whether our approach is correct. 8. Q&A 1) Among config items, what do you think about those which affect other items, such as removing inline? We think separately for those which affect over all. 2) How about considering .o based? We are working config based as interface with human is config. 3) Comparison among versions seems difficult for 2.6, as changes are big. Want to see on 2.4 too. We feel we need to see 2.4, as comparison between 2.4 and 2.6 make it clear the impact of 2.6 transiton on code size.