| |||||||||||||
Time to slow down?Time to slow down?Posted May 8, 2008 19:58 UTC (Thu) by jbailey (subscriber, #16890)In reply to: Time to slow down? by jordip Parent article: Time to slow down?
I'm curious what the stats are of code with the drivers removed. Code growth through drivers and archs that 95% people of people won't run in their kernel isn't that interesting. I have a vague feeling (without proof) that the core kernel sans drivers is not growing that dramatically. Subsystems already have their own maintainers and review systems. Scaling then happens with the splitting into subsystems and driver maintainers, etc. So not actually a problem in the longer term, even though total LoC churn would be very high.
(Log in to post comments)
Time to slow down? Posted May 9, 2008 18:16 UTC (Fri) by gregkh (subscriber, #8) [Link] The kernel code is growing in an exact proportion to the amount it contains within the kernel itself. So, for example, the core kernel makes up 5% of the overall size. And exactly 5% of the changes happen in the core kernel code itself. Same goes for every other category of the kernel code, it's pretty amazing. I have a script that digs all of these numbers out of the changelogs on my kernel.org directory for these kinds of statistics.
|
|||||||||||||