Sorry, that track doesn't exist or has been deleted.

Tracks are used to submit both suggestions for complete Microconferences to be held within the Linux Plumbers Conference, as well as for suggestions of appropriate topics for individual Microconferences.

For discussion of topic ideas, please see the Wiki

Please use the Microconference Suggestions track to suggest new titles; if the programme committee approves, we'll move the suggestion to become a new Track.

The Linux Plumbers Conference currently has room for about ten to twelve Microconferences, so less popular ones might not make the cut for inclusion in the conference proper.  If this happens, please consider a BoF session instead.


Audio support on Linux is currently undergoing a rapid evolution, with a growing expectation on the part of users that everything will work off the shelf with no manual configuration. This is a particular problem at the system integration level, with many diverse audio sources and sinks (both physical and software) in the system which need to be managed together to provide the functionality which end users expect.

The problems are most complex in the embedded world due to both the lack of hardware standards and big developments in both the audio hardware present on embedded systems such as mobile phones and the feature sets supported at the user level.

In this track we want to cover the whole audio stack, from userspace sound servers and interfaces to low-level audio driver architecture. We’ll focus on new audio features for audio production, as well as technology for the classic desktop and cover mobile platforms as well.


Boot and Init

This miniconf is focused on the linux init system, improving boot speed, and init infrastructure including upstart, systemd, udev, among others.






Possible track for capturing embedded/small system topics

  • Standardize boot interface for ARM
  • Device driver and the device tree
  • Core plumbing required in small systems.
  • Running mainstream distros on ARM devices

File and Storage Systems

The track will deal with issues around file and storage systems in Linux, from the kernel space up to user space. Getting applications to work well and get tuned properly, how to benchmark administer, etc.

The track should draw developers for the various components, vendors of storage systems (both traditional storage and newer devices), kernel developers.


High Availability Clustering


Over the last very few years, High-Availability clustering on Linux has seen significant convergence and the emergence of a single stack, based on the fs/dlm code on the kernel-side, and around corosync/openais/Pacemaker etcetera on the user-space part. This is now being adopted by Red Hat, Ubuntu, Novell/SUSE, Debian and others.

Work remains to be done on mapping a roadmap for resource agent merges, more core library work such as logging infrastructure, roadmap alignment between components and stakeholders, packaging details, …

Multimedia Infrastructure

A discussion about the state of video capture device, video decoding device, video display device, and remote control integration in the linux kernel and userspace.

Many Linux-based video capture setups require an infrared transmitter to change channels on a set top box, due to the video stream otherwise being encrypted or otherwise inaccessible. And if you’re capturing video, you probably need a way to play it back, which required either enough cpu or specialized hardware to decode the video, and a video card to output to a monitor or television to actually view it. And then you probably want to be able to control playback using a remote control.

Integrating all these things together can be a challenge, but there’s a lot we can do to make it less challenging, starting with kernel-level driver integration and auto-configuration, which we can then extend outward to end-user application.


Power Management

Discussions about all topics related to power management

Real Time

The Real-Time preemption patch started in 2004 and large parts of the development has been integrated into the mainline kernel and into the affected user space libraries. There are still parts which need to be worked on for upstream inclusion.

The Real-Time track provides a discussion forum for ongoing and related work.



Tracing within the Linux kernel and userland helps in seeing how and why the system acts the way it does. Tracing facilitates the debuging of the system as well as understanding the reason the system behaves in a certain way.

Currently, Ftrace is the major tracing infrastructure of the Linux kernel, but perf is starting to overlap in its features. Not to mention LTTng, which is not part of the mainline kernel but is being used by companies with a patched kernel. Integration of these tracers would benefit the user community greatly, but there are some technical (as well as social) issues in making them collaborate better.


User Visible Network Issues

Discussion of device naming, Network Manger, Conman etc.



LPC is particular well suited for work in progress and subjects that needs discussion and collaboration between communities, for example between KVM/QEMU and the Linux Kernel community. We expect strong participation of kernel developers at LPC, and likely also from the desktop community (GNOME/KDE/Xorg).

Note this is focused on general Linux Virtualization, it is not limited to a specific hypervisor.

If you have a virtualization related project proposal, please add it to this page. Please make sure to tag additional suggestions with your name. Topics could be in the area of (but not limited to):

  • Kernel ↔ KVM/QEMU interaction
  • IO Performance improvements
  • NUMA awareness
  • Migration
  • Support for new hardware features, and/or provide guest access to these features.
  • Virtualization management, user interfaces, and desktop integration
  • Consumer Electronics device emulation
  • Custom platform configuration and coordination with the kernel
Back to proposals