- Make it work: see
- <a href="http://bugs.debian.org/695850">http://bugs.debian.org/695850</a>
- </li>
- </ul>
-</div>
-
-<div class="slide">
- <h1>Transcendent memory [3.0-3.5]</h1>
- <ul class="incremental">
- <li>
- Abstract storage for memory pages, expected to be slower than
- regular memory but faster than disk
- </li>
- <li>
- Can provide a second layer of page cache (cleancache and frontswap)
- </li>
- <li>
- Pages stored by hypervisor (Xen), compressed local memory
- (zcache) or cluster of machines (RAMster)
- </li>
- <li>
- Not yet enabled in Debian kernels, and needs some thought about
- configuration
- </li>
- <li>
- Make it work: see
- <a href="https://lwn.net/Articles/454795/">https://lwn.net/Articles/454795/</a>
- and send proposal to debian-kernel
- </li>
- </ul>
-</div>
-
-<div class="slide">
- <h1>New KMS drivers [3.3-3.10]</h1>
- <ul class="incremental">
- <li>
- DRM/KMS drivers added for old, new and virtual hardware -
- AST, DisplayLink, Hyper-V, Matrox G200, QEMU Cirrus
- </li>
- <li>
- Should be more robust than purely user-mode drivers, and
- compatible with Secure Boot
- </li>
- <li>
- Current X drivers don't work with these, so the kernel drivers
- are disabled for now
- </li>
- <li>
- Make it work: join the X Strike Force and package the new X
- drivers
- </li>
- </ul>
-</div>
-
-<div class="slide">
- <h1>Module signing [3.7]</h1>
- <ul class="incremental">
- <li>
- Kernel modules can be signed at build time, and the kernel
- configured to refuse loading unsigned modules
- </li>
- <li>
- Necessary but not sufficient to implement Secure Boot -
- we would also need signed kernel images and some other
- restrictions when booted in this mode
- </li>
- <li>
- Make Secure Boot work: come to the meeting on Tuesday
- </li>
- </ul>
-</div>
-
-<div class="slide">
- <h1>More support for discard</h1>
- <ul class="incremental">
- <li>
- Flash devices (and thin-provisioned SANs) can be more efficient
- if the filesystem 'discards' unused disk space
- </li>
- <li>
- Requires support in hardware, driver, filesystem and any layered
- device drivers - e.g. LVM, RAID (added in 3.7)
- </li>
- <li>
- Must be explicitly enabled, but d-i doesn't do this by default