28.08.2015 Views

The Design and Implementation of the Anykernel and Rump Kernels

1F3KDce

1F3KDce

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

231<br />

80<br />

70<br />

60<br />

seconds<br />

50<br />

40<br />

30<br />

20<br />

10<br />

0<br />

bigcp<br />

treecp<br />

kern<br />

rump r/w<br />

Figure 4.18:<br />

regular file.<br />

Performance <strong>of</strong> a journaled FFS with <strong>the</strong> file system on a<br />

As expected, journaling does not affect writing one large file, since a majority <strong>of</strong><br />

<strong>the</strong> operations involve data <strong>and</strong> not metadata (earlier, we quoted <strong>the</strong> figure 98.5%<br />

<strong>of</strong> <strong>the</strong> operations). In <strong>the</strong> directory write test a rump kernel still outperforms <strong>the</strong><br />

regular kernel. As above, we conclude this is due to better prefaulting <strong>of</strong> metadata<br />

in <strong>the</strong> rump kernel backend.<br />

4.6.6 Backend: Networking<br />

We measured <strong>the</strong> latency <strong>of</strong> ICMP pinging <strong>the</strong> TCP/IP stack on common virtualization<br />

technologies. <strong>The</strong> ping response is h<strong>and</strong>led by <strong>the</strong> TCP/IP stack in <strong>the</strong><br />

kernel, so <strong>the</strong>re is no process scheduling involved. Since User Mode Linux requires<br />

a Linux host, <strong>the</strong> test against UML was run on Linux. We ran <strong>the</strong> Xen test with<br />

Linux dom0/domU as well.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!