X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=index.html;h=68e0fe8758e490ef43e0eff170aae6764ea21ba5;hb=beefb0772ed40f965df983c7d06823dd44338d57;hp=9822d2ed071140150b5be185403c5b2f43659b20;hpb=147b8181c99dbe6a5f3a98eab94d67fde1962517;p=kernel-news-talk.git
diff --git a/index.html b/index.html
index 9822d2e..68e0fe8 100644
--- a/index.html
+++ b/index.html
@@ -4,7 +4,7 @@
-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 first
+ 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,277 @@
-
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
+ Team device driver: userland package (libteam) was uploaded in
+ October
- Basic configuration can be done with ip, but it really
- needs new tools - teamd, teamnl, etc.
+ Transcendent memory: frontswap, zswap and Xen tmem will be
+ enabled in next kernel upload
+ Module signing: still not enabled, but probably will be if we
+ do Secure Boot
-
Transcendent memory [3.0-3.5]
+
Recap of last year's features (2)
- Abstract storage for memory pages, expected to be slower than
- regular memory but faster than disk
+ More support for discard: still not enabled at install time
+ (#690977)
- Can provide a second layer of page cache (cleancache and frontswap)
+ More support for containers: XFS was fixed, and user namespaces
+ have been enabled
- Pages stored by hypervisor (Xen), compressed local memory
- (zcache) or cluster of machines (RAMster)
+ bcache: userland package (bcache-tools) still not quite ready
+ (#708132)
- Not yet enabled in Debian kernels, and needs some thought about
- configuration
+ 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.
+
+
+
+
+
Unnamed temporary files [3.11]
+
- Make it work: see
- https://lwn.net/Articles/454795/
- and send proposal to debian-kernel
+ Open directory with option O_TMPFILE to create an
+ unnamed temporary file on that filesystem
+
+
+ As with tmpfile(), the file disppears on
+ last close()
+
+
+ File can be linked into the filesystem using
+ linkat(..., AT_EMPTY_PATH), allowing for 'atomic'
+ creation of file with complete contents and metadata
+
+
+ Not supported on all filesystem types, so you will usually need
+ a fallback
-
New KMS drivers [3.3-3.10]
+
Network busy-polling [3.11] (1)
+
A conventional network request/response process looks like:
+
+
+
+ Task calls send(); network stack constructs a
+ packet; driver adds it to hardware Tx queue
+
+
+ Task calls poll() or recv(), which blocks;
+ kernel puts it to sleep and possibly idles the CPU
+
+
+ Network adapter receives response and generates IRQ, waking
+ up CPU
+
+
+ Driver's IRQ handler schedules polling of the hardware Rx
+ queue (NAPI)
+
+
+ Kernel runs the driver's NAPI poll function, which passes
+ the response packet into the network stack
+
+
+ Network stack decodes packet headers and adds packet to
+ the task's socket
+
+
+ Network stack wakes up sleeping task; scheduler switches
+ to it and the socket call returns
+
+
+
+
+
+
+
Network busy-polling [3.11] (2)
- DRM/KMS drivers added for old, new and virtual hardware -
- AST, DisplayLink, Hyper-V, Matrox G200, QEMU Cirrus
+ If driver supports busy-polling, it tags each packet with
+ the receiving NAPI context, and kernel tags sockets
- Should be more robust than purely user-mode drivers, and
- compatible with Secure Boot
+ When busy-polling is enabled, poll()
+ and recv() call the driver's busy poll function to
+ check for packets synchronously (up to some time limit)
- Current X drivers don't work with these, so the kernel drivers
- are disabled for now
+ If the response usually arrives quickly, this reduces overall
+ request/response latency as there are no context switches and
+ power transitions
- Make it work: join the X Strike Force and package the new X
- drivers
+ Time limit set by sysctl (net.busy_poll,
+ net.busy_read) or socket option (SOL_SOCKET,
+ SO_BUSY_POLL); requires tuning
-
Module signing [3.7]
+
Lustre filesystem [3.12]
+
+
+ A distributed filesystem, popular for cluster computing
+ applications
+
+
+ Developed out-of-tree since 1999, but now added to Linux staging
+ directory
+
+
+ Was included in squeeze but dropped from wheezy as it didn't
+ support Linux 3.2
+
+
+ Userland is now missing from Debian
+
+
+
+
+
+
Btrfs offline dedupe [3.12]
- Kernel modules can be signed at build time, and the kernel
- configured to refuse loading unsigned modules
+ Btrfs generally does COW rather than updating in-place, allowing
+ snapshots and file copies to defer the actual copying and save
+ space
+
+
+ Filesystems may still end up with multiple copies of the same
+ file content
- Necessary but not sufficient to implement Secure Boot -
- we would also need signed kernel images and some other
- restrictions when booted in this mode
+ Btrfs doesn't actively merge these duplicates, but userland can
+ tell it to do so
- Make Secure Boot work: come to the meeting on Tuesday
+ Many file dedupe tools are packaged for Debian, but not one that
+ works with this Btrfs feature, e.g. bedup
-
More support for discard
+
nftables [3.13]
- Flash devices (and thin-provisioned SANs) can be more efficient
- if the filesystem 'discards' unused disk space
+ Linux has several firewall APIs - iptables, ip6tables, arptables
+ and ebtables
- Requires support in hardware, driver, filesystem and any layered
- device drivers - e.g. LVM, RAID (added in 3.7)
+ All limited to single protocol, and need a kernel module for
+ each match type and each action
- Must be explicitly enabled, but d-i doesn't do this by default
+ Kernel's internal netfilter API is more flexible
- Make it work: fix http://bugs.debian.org/690977
+ nftables exposes more of this flexibility, allowing userland
+ to provide firewall code for a specialised VM (similar to BPF)
+
+
+ nftables userland tool uses this API and is already packaged
+
+
+ Eventually, old APIs will be removed and old userland
+ tools must be ported to use nftables
-
User namespaces [3.7]
+
User-space lockdep [3.14]
+
+
+ Kernel threads and interrupts all run in same address space,
+ using several different synchronisation mechanisms
+
+
+ Easy to introduce bugs that can result in deadlock, but hard to
+ reproduce them
+
+
+ Kernel's 'lockdep' system dynamically tracks locking operations
+ and detects potential deadlocks
+
+
+ Now available as a userland library! Except we need to package
+ it (build from linux-tools source package)
+
+
+
+
+
+
arm64 and ppc64el ports
- One of the last missing pieces for OpenVZ-like containers
+ 'arm64' architecture was added in Linux 3.7, but was not yet
+ usable, and no real hardware was available at the time
+
+
+ Upstream Linux arm64 kernel, and Debian packages, should now run
+ on emulators and real hardware
+
+
+ 'powerpc' architecture has been available for many years,
+ but didn't support kernel running little-endian
+
+
+ Linux 3.13 added little-endian kernel suport, along with new
+ userland ELF ABI variant - we call it ppc64el
+
+
+ Both ports now being bootstrapped in unstable and are candidates
+ for jessie release
+
+
+
+
+
+
File-private locking [3.15]
+
+
+ POSIX says that closing a file descriptor removes
+ the process's locks on that file
+
+
+ What if process has multiple file descriptors for the same
+ file? It loses all locks obtained through any descriptor!
- Each user namespace has its own root user with
- privileges over the users and processes in that namespace - but
- not the whole system
+ Multithreaded processes may require serialisation around
+ file open/close to ensure they open each file exactly once
- Currently somewhat experimental, and requires filesystem
- changes which haven't been done for NFS or XFS
+ Hard and symbolic links can hide that two files are really the
+ same
- Make it work: send patches to upstream NFS and XFS developers
- (this one's hard)
+ Linux now provides file-private locks, associated with a
+ specific open file and removed when last descriptor for the
+ open file is closed