-What's new in the Linux kernel - DebConf 2013
+What's new in the Linux kernel - DebConf 2014
@@ -39,7 +39,7 @@
@@ -50,6 +50,7 @@
What's new in the Linux kernel
+
and what's missing in Debian
Ben Hutchings
@@ -58,13 +59,13 @@
Professional software engineer by day, Debian developer by night
+ (or sometimes the other way round)
Regular Linux contributor in both roles since 2008
- Maintaining a net driver in my day job, plus core networking
- and PCI code as necessary
+ Working on various drivers and kernel code in my day job
Debian kernel team member, now doing most of the unstable
@@ -83,10 +84,15 @@
Linux is released about 5 times a year (plus stable updates
every week or two)
+
+
+ ...though some features aren't ready to use when they firat
+ appear in a release
+
+
- For 'wheezy' we chose to freeze with Linux 3.2, which was
- getting pretty old by the time of release
+ Since my talk last year, Linus has made 6 releases (3.11-3.16)
Good news: we have lots of new kernel features in testing/unstable
@@ -98,127 +104,68 @@
-
Team device driver [3.3]
+
Recap of last year's features (1)
- Alternative to the bonding driver - simpler, modular, high-level
- control deferred to userland
-
-
- Basic configuration can be done with ip, but it really
- needs new tools - teamd, teamnl, etc.
-
-
- Make it work: see
- http://bugs.debian.org/695850
+ Team device driver: userland package (libteam) was uploaded in
+ October
-
-
-
-
-
Transcendent memory [3.0-3.5]
-
- Abstract storage for memory pages, expected to be slower than
- regular memory but faster than disk
+ Transcendent memory: frontswap, zswap and Xen tmem will be
+ enabled in next kernel upload
- Can provide a second layer of page cache (cleancache and frontswap)
+ New KMS drivers: should all work with current Xorg drivers
- Pages stored by hypervisor (Xen), compressed local memory
- (zcache) or cluster of machines (RAMster)
-
-
- Not yet enabled in Debian kernels, and needs some thought about
- configuration
-
-
- Make it work: see
- https://lwn.net/Articles/454795/
- and send proposal to debian-kernel
+ Module signing: still not enabled, but probably will be if we
+ do Secure Boot
-
New KMS drivers [3.3-3.10]
+
Recap of last year's features (2)
- DRM/KMS drivers added for old, new and virtual hardware -
- AST, DisplayLink, Hyper-V, Matrox G200, QEMU Cirrus
+ More support for discard: still not enabled at install time
+ (#690977)
- Should be more robust than purely user-mode drivers, and
- compatible with Secure Boot
+ More support for containers: XFS was fixed, and user namespaces
+ have been enabled
- Current X drivers don't work with these, so the kernel drivers
- are disabled for now
+ bcache: userland package (bcache-tools) still not quite ready
+ (#708132)
- Make it work: join the X Strike Force and package the new X
- drivers
+ ARMv7 multiplatform: d-i works on some platforms but
+ I'm still not sure which. Some progress on GPU drivers, but not
+ in Debian yet.
-
Module signing [3.7]
-
-
- Kernel modules can be signed at build time, and the kernel
- configured to refuse loading unsigned modules
-
-
- Necessary but not sufficient to implement Secure Boot -
- we would also need signed kernel images and some other
- restrictions when booted in this mode
-
-
- Make Secure Boot work: come to the meeting on Tuesday
-
-
-
-
-
-
More support for discard
-
-
- Flash devices (and thin-provisioned SANs) can be more efficient
- if the filesystem 'discards' unused disk space
-
-
- Requires support in hardware, driver, filesystem and any layered
- device drivers - e.g. LVM, RAID (added in 3.7)
-
-
- Must be explicitly enabled, but d-i doesn't do this by default
-
- One of the last missing pieces for OpenVZ-like containers
+ Open directory with option O_TMPFILE to create an
+ unnamed temporary file on that filesystem
- Each user namespace has its own root user with
- privileges over the users and processes in that namespace - but
- not the whole system
+ As with tmpfile(), the file disppears on
+ last close()
- Currently somewhat experimental, and requires filesystem
- changes which haven't been done for NFS or XFS
+ File can be linked into the filesystem using
+ linkat(..., AT_EMPTY_PATH), allowing for 'atomic'
+ creation of file with complete contents and metadata
- Make it work: send patches to upstream NFS and XFS developers
- (this one's hard)
+ Not supported on all filesystem types, so you will usually need
+ a fallback