His renowned Kernel Report has been presented to audiences worldwide, and this year will mark his fourth appearance at Linux.conf.au, in Melbourne, Australia.
Here, Corbet offers Computerworld readers a sneak peek at the major themes behind this year's Kernel Report.
What is the main theme of your talk at Melbourne's Linux Conference?
The real purpose of my talk is to bring attendees up-to-date with regard to what is happening in the kernel development community. It is a fast-moving project which is very hard to keep up with - the linux-kernel mailing list, alone, can run up to 500 highly technical messages per day. I do follow this community, though, and have gotten reasonably good at summarising what is happening there - and making hand-waving predictions about what will be happening in the near future.
How has the kernel development process gone over the past year? What were the major happenings?
The process is running quite smoothly, with four major kernel releases (2.6.20 through .23) being made, and 2.6.24 being brought close to release. I anticipate it will come out just before linux.conf.au begins.
I am confident that, five years from now, we will say that we were able to accept unprecedented amounts of new code at a sustained rate for years while improving the quality of the final product.
Major events over the last year include the incorporation of several virtualisation implementations (KVM, Lguest, Xen), the dynamic tick patches, a completely new wireless networking stack, the CFS process scheduler, and much, much more.
Is the patch flow rate continuing at a high rate?
It is, in fact, increasing, with the 2.6.24 kernel having the highest patch rate yet. Almost 10,000 separate changesets were merged in this development cycle, resulting in the addition of about 300,000 lines of code - and the modification of many more. One big change (the merger of the i386 and x86-64 architecture code) accounted for a lot of patches, but it was still a tiny part of the whole.
Has the number of developers contributing increased, and has the breakdown of who they work for changed much since last year's Kernel report?
The number of developers is approximately the same - over the course of one year, about 2,000 individual developers will contribute at least one patch to the kernel. I have an unquantified sense that more of these developers are being more active, though.
Once upon a time, the top 20 developers were responsible for a large majority of the code going into any given kernel release. Now they barely do 20%. When the kernel summit program committee tried to identify the 70 or so most important developers, we had a very hard time narrowing down the list. The development community is quite broad, and is becoming more so.
Are there any new big companies paying for development?
The list of companies has stayed relatively static, though it does get shuffled a bit from one release to the next, depending on what gets merged into the kernel in that cycle. One recent addition is Movial, which has hired a very active kernel developer and immediately found its way onto the top-20 list.