</ul>
</div>
-<div class="slide">
- <h1>Lustre filesystem [3.12]</h1>
- <ul>
- <li>
- A distributed filesystem, popular for cluster computing
- applications
- </li>
- <li>
- Developed out-of-tree since 1999, but now added to Linux staging
- directory
- </li>
- <li>
- Was included in squeeze but dropped from wheezy as it didn't
- support Linux 3.2
- </li>
- <li>
- Userland is now missing from Debian
- </li>
- </ul>
-</div>
-
<div class="slide">
<h1>Network busy-polling [3.11] (1)</h1>
<p>A conventional network request/response process looks like:</p>
</ul>
</div>
+<div class="slide">
+ <h1>Lustre filesystem [3.12]</h1>
+ <ul>
+ <li>
+ A distributed filesystem, popular for cluster computing
+ applications
+ </li>
+ <li>
+ Developed out-of-tree since 1999, but now added to Linux staging
+ directory
+ </li>
+ <li>
+ Was included in squeeze but dropped from wheezy as it didn't
+ support Linux 3.2
+ </li>
+ <li>
+ Userland is now missing from Debian
+ </li>
+ </ul>
+</div>
+
<div class="slide">
<h1>Btrfs offline dedupe [3.12]</h1>
<ul class="incremental">
and ebtables
</li>
<li>
- All require a specific kernel module for each type of match
- and each possible action
+ All limited to single protocol, and need a kernel module for
+ each match type and each action
</li>
<li>
- Userland could only use the four protocol-specific APIs,
- although the internal netfilter API is more flexible
+ Kernel's internal netfilter API is more flexible
</li>
<li>
nftables exposes more of this flexibility, allowing userland
nftables userland tool uses this API and is already packaged
</li>
<li>
- Eventually, the old APIs will be removed and the old userland
+ Eventually, old APIs will be removed and old userland
tools must be ported to use nftables
</li>
</ul>