Update latencies table

1 files changed, 19 insertions, 3 deletions

diff --git a/release_notes.md b/release_notes.md
index db8a775f..7912d06e 100644
--- a/release_notes.md
+++ b/release_notes.md
@@ -12,7 +12,13 @@ library for Boost and the C++ standard.
 It is a complete rewrite after a Boost peer review in August 2015. Its github
 source code repository lives at https://github.com/ned14/boost.afio.
 
-Why you might need AFIO: Average 4Kb transfer latencies for the physical hardware:
+<table border="0" cellpadding="4">
+<tr>
+<th colspan="2">Why you might need AFIO</th>
+</tr>
+<tr>
+<td>
+Average 4Kb transfer latencies for the physical hardware:
 - Average read spinning rust hard drive latency @ QD1: **7000us**
 - Average read SATA flash drive latency @ QD1: **800us**
 - Average `memcpy(4Kb)` latency: **500us** (main memory) to **90us** (L2 cache)
@@ -20,14 +26,24 @@ Why you might need AFIO: Average 4Kb transfer latencies for the physical hardwar
 - Average RTT UDP packet latency over a LAN: **60us**
 - Average read XPoint drive latency @ QD1: **10us**
 - Average RTT PCIe latency: **0.5us**
-
-Why you might need AFIO: Max bandwidth for the physical hardware:
+</td>
+<td>
+Max bandwidth for the physical hardware:
 - DDR4 2133: **30Gb/sec** (main memory)
 - x4 PCIe 4.0: **7.5Gb/sec** (arrives end of 2017, the 2018 NVMe drives will use PCIe 4.0)
 - x4 PCIe 3.0: **3.75Gb/sec**
 - 2017 XPoint drive (x4 PCIe 3.0): **2.5Gb/sec**
 - 2017 NVMe flash drive (x4 PCIe 3.0): **2Gb/sec**
 - 10Gbit LAN: **1.2Gb/sec**
+</td>
+<td>
+Average 4Kb transfer latencies for the software with `O_DIRECT`:
+- Average read spinning rust hard drive latency @ QD1: **TODO**
+- Average read SATA flash drive latency @ QD1: **TODO**
+- Average read NVMe flash drive latency @ QD1: **TODO**
+</td>
+</tr>
+</table>
 
 \note Note that this code is of late alpha quality. It's quite reliable, but be careful when using it!