Aug 24 – 28, 2020
US/Pacific timezone

Planning code obsolescence

Aug 25, 2020, 7:00 AM
Microconference3/Virtual-Room (LPC Virtual)


LPC Virtual

linux/arch/* MC linux/arch/* MC


Arnd Bergmann (Linaro)


The majority of the code in the kernel deals with hardware that was made a long time ago, and we are regularly discussing which of those bits are still needed. In some cases (e.g. 20+ year old RISC workstation support), there are hobbyists that take care of maintainership despite there being no commercial interest. In other cases (e.g. x.25 networking) it turned out that there are very long-lived products that are actively supported on new kernels.

When I removed support for eight instruction set architectures in 2018, those were the ones that no longer had any users of mainline kernels, and removing them allowed later cleanup of cross-architecture code that would have been much harder before.

I propose adding a Documentation file that keeps track of any notable kernel feature that could be classified as "obsolete", and listing e.g. following properties:

  • Kconfig symbol controlling the feature
  • How long we expect to keep it as a minimum
  • Known use cases, or other reasons this needs to stay
  • Latest kernel in which it was known to have worked
  • Contact information for known users (mailing list, personal email)
  • Other features that may depend on this
  • Possible benefits of eventually removing it

With that information, my hope is that it becomes easier to plan when some code can be removed after the last users have stopped upgrading their kernels, while also preventing code from being removed that is actually still in active use.

In the discussion at the linux/arch/* MC, I would hope to answer these questions:

  • Do other developers find this useful to have?
  • Where should the information be kept (Documentation/*, Kconfig, MAINTAINERS,, ...)
  • Which information should be part of an entry?
  • What granularity should this be applied to -- only high-level features like CPU architectures and subsystems, or individual drivers and machines?
I agree to abide by the anti-harassment policy I agree

Primary author

Presentation materials

Diamond Sponsor

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Catchboxes Sponsor

Conference Services Provided By