LPC 2021 Microconferences
CFP Ends: TBD
The Containers and Checkpoint/Restore Microconference focuses on both userspace and kernel related work. The micro-conference targets the wider container ecosystem ideally with participants from all major container runtimes as well as init system developers.
Contributions to the micro-conference are expected to be problem statements, new use-cases, and feature proposals both in kernel- and userspace.
- How to best use CAP_CHECKPOINT_RESTORE in CRIU to make it possible to run checkpoint/restore as non-root (with CAP_CHECKPOINT_RESTORE)
- Extending the idmapped mount feature to unprivileged containers, i.e. agreeing on a sane and safe delegation mechanism with clean semantics.
- Porting more filesystems to support idmapped mounts.
- Making it possible for unprivileged containers and unprivileged users in general to install fanotify subtree watches.
- Discussing and agreeing on a concept of delegated mounts, i.e. the ability for a privileged process to create a mount context that can be handed of to a lesser privileged process which it can interact with safely.
- Fixing outstanding problems in the seccomp notifier to handle syscall preemption cleanly. A patchset for this is already out but we need a more thorough understanding of the problem and its proposed solution.
- With more container engines and orchestrators supporting checkpoint/restore there has come up the idea to provide an optional interface with which applications can be notified that they are about to be checkpointed. Possible example is a JVM that could do cleanups which do not need to be part of a checkpoint.
- Discussing an extension of the seccomp API to make it possible to ideally attach a seccomp filter to a task, i.e. the inverse of the current model instead of caller-based seccomp sandboxing enabling full supervisor-based sandboxing.
- Integration of the new Landlock LSM into container runtimes.
- Although checkpoint/restore can handle cgroupv1 correctly the cgroupv2 support is very limited and there is a need to figure out what is still missing to have v2 supported just as good as v1.
- Isolated user namespaces (each with full 32bit uid/gid range) and easier way for users to create and manage them.
- Figure out what is missing on the checkpoint/restore level and maybe the container runtime level to support optimal checkpoint/restore integration on the orchestration level. Especially the pod concept of Kubernetes introduces new challenges which have not been part of checkpoint/restore before (containers sharing namespaces for example).
If you are interested in participating in this microconference and have topics to propose, please use the CfP process, and select "Containers and Checkpoint/Restore MC" for the "Track". More topics will be added based on CfP for this microconference.
- Stéphane Graber <email@example.com>, Mike Rapoport <firstname.lastname@example.org>, Adrian Reber <email@example.com>, and Christian Brauner <firstname.lastname@example.org>
CFP Ends: TBD
The Confidential Computing microconference focuses on solutions to the development of using the state of the art encyption technologies for live encryption of data, and how to utilize the technologies from AMD (SEV), Intel (TDX), s390 and ARM Secure Virtualization for secure computation of VMs, containers and more.
- Live Migration of Confidential VMs
- Lazy Memory Validation
- APIC emulation/interrupt management
- Debug Support for Confidential VMs
- Required Memory Management changes for memory validation
- Safe Kernel entry for TDX and SEV exceptions
- Requirements for Confidential Containers
- Trusted Device Drivers Framework and driver fuzzing
- Remote Attestation
For more references, see:
If you are interested in participating in this microconference and have topics to propose, please use the CfP process, and select "Confidential Computing MC" for the "Track". More topics will be added based on CfP for this microconference.
- Joerg Roedel <email@example.com>
CFP Ends: TBD
The Scheduler microconference focuses on deciding what process gets to run when and for how long. With different topologies and workloads, it is no easy task to give the user the best experience possible. Schedulers are one of the most discussed topics at the Linux Kernel Mailing List, but many of these topics need further discussion in a conference format. Indeed, the scheduler microconference is responsible for many topics to make progress.
- Cgroup interface and other updates for core-scheduling
- Cgroup and SCHED_DEADLINE
- Capacity Awareness – For busy systems
- Interrupt Awareness
- Load Balancing:
If you are interested in participating in this microconference and have topics to propose, please use the CfP process, and select "Scheduler MC" for the "Track". More topics will be added based on CfP for this microconference.
- Dhaval Giani <firstname.lastname@example.org>
- Daniel Bristot de Oliveira <email@example.com>
- Chris Hyser <firstname.lastname@example.org>
- Juri Lelli <email@example.com>
- Vincent Guittot <firstname.lastname@example.org>
CFP Ends: TBD
The Performance and Scalability microconference focuses on enhancing performance and scalability in both the Linux kernel and userspace projects. In fact, one of the purposes of this microconference is for developers from different projects to meet and collaborate – not only kernel developers but also researchers doing more experimental work. After all, for the user to see good performance and scalability, all relevant projects must perform and scale well.
Because performance and scalability are very generic topics, this track is aimed at issues that may not be addressed in other, more specific sessions. The structure will be similar to what was followed in previous years, including topics such as synchronization primitives, bottlenecks in memory management, testing/validation, lockless algorithms and RCU, among others.
- Seamless hypervisor update with IOMMU-type-agnostic, directly-attached devices and virtual functions. Related projects are VMM Fast Restart, PKRAM, and MMU enabled kexec relocation for arm64.
- Performance characteristics of RT spinlocks.
- Accounting CPU-intensive kernel threads in the CPU controller via remote charging (thread 1, thread 2, thread 3).
- Design discussion and performance characteristics of Maple Tree (lwn article).
- mmap_sem contention in procfs (test code, gitweb).
- NUMA-aware spinlocks: (series, lwn article).
- futex2: attempts to tackle the performance limitations of the single NUMA node hash table.
- Batching optimizations in the internals of get_user_pages() and put_user_pages().
- Fast kdump for embedded devices.
If you are interested in participating in this microconference and have topics to propose, please use the CfP process, and select "Performance and Scalability MC" for the "Track". More topics will be added based on CfP for this microconference.
- Davidlohr Bueso <email@example.com>
- Daniel Jordan <firstname.lastname@example.org>
- Pavel Tatashin <email@example.com>
CFP Ends: TBD
The IoThree's Company microconference is moving into its third year at Plumbers. Talks cover everything from the real-time operating systems in wireless microcontrollers, to products and protocols, to Linux kernel and tooling integration, userspace, and then all the way up to backing cloud services. The common ground we all share is an interest in improving the developer experience within the Linux ecosystem.
- Automotive initiative involving vehicle control, navigation, and autonomous driving
- Real-Time (RT) Linux and Safety Critical (ELISA) projects
- Linux kernel / wpan-tools MAC Layer patch integration ongoing to support scanning, joining, forming networks
- The wpanusb module is close to being integrated in Linux to provide a common transceiver interface for RIOT OS, Zephyr and others
- Support for multiple network interface autoconfiguration in Zephyr
- Greybus pthread and dynamic thread stack support for Zephyr
- Greybus minimize socket / certificate overhead for Zephyr
If you are interested in participating in this microconference and have topics to propose, please use the CfP process, and select "IoT's Company MC" for the "Track". More topics will be added based on CfP for this microconference.
- Christopher Friedt <firstname.lastname@example.org>
- Jason Kridner <email@example.com>
- Drew Fustini <firstname.lastname@example.org>
CFP Ends: TBD
The Tracing microconference focuses on improvements of the Linux kernel tracing infrastructure. Ways to make it more robust, faster and easier to use. Also focus on the tooling around the tracing infrastructure will be discussed. What interfaces can be used, how to share features between the different toolkits and how to make it easier for users to see what they need from their systems.
Tracepoints that allow faults. It may be necessary to read user space address, but currently because tracepoints disable preemption, it can not sleep, nor fault. And then there's the possibilities of causing locking issues.
Function parameter parsing. Now that on x86 function tracing has full access to the arguments of a function, it is possible to record them as they are being traced. But knowing how to read the parameters may be difficult, because it is necessary to know the prototype of the function to do so. Having some kind of mapping between functions and how to read their parameters would be useful. Using BTF is a likely candidate.
Python interface. Working on getting the libraries a python interface to allow full tracing from within python scripts.
Tracing containers. What would be useful to expose on creating and running containers.
If you are interested in participating in this microconference and have topics to propose, please use the CfP process, and select "Tracing MC" for the "Track". More topics will be added based on CfP for this microconference.
- Steven Rostedt <email@example.com>
- Yordan Karadzhov <firstname.lastname@example.org>