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.

193<br />

original<br />

rump kernel backend<br />

FFS SLOC 1748 247<br />

supported file FFS FFS, ext2, FAT,<br />

systems<br />

SysVBFS<br />

FFS effort > 2.5 weeks (100 hours) 2hours<br />

total effort 7weeks(280hours) 2 days (16 hours)<br />

Table 4.2:<br />

makefs implementation effort comparison.<br />

In <strong>the</strong> original version <strong>of</strong> makefs all <strong>of</strong> <strong>the</strong> phases were implemented in a single C<br />

program. Notably, phase 4 is <strong>the</strong> only one that requires a duplicate implementation<br />

<strong>of</strong> features <strong>of</strong>fered by <strong>the</strong> kernel file system driver.<br />

We implemented makefs using a rump kernel backend for phase 4. We partially<br />

reused code from <strong>the</strong> original makefs, since we had to analyze <strong>the</strong> source tree to<br />

determine <strong>the</strong> image size (phases 1&2). We rely on an external newfs/mkfs program<br />

for creating an empty file system image (phase 3). For phase 4 we use fs-utils to<br />

copy a directory hierarchy to a file system image.<br />

For phase 3, we had to make sure that <strong>the</strong> mkfs/newfs utility can create an empty<br />

file system in a regular file. Historically, such utilities operate on device special<br />

files. Out <strong>of</strong> <strong>the</strong> supported file systems, we had to add support for regular files to<br />

<strong>the</strong> NetBSD FAT <strong>and</strong> SysVBFS file system creation utilities. Support for each was<br />

approximately 100 lines <strong>of</strong> modification.<br />

We obtained <strong>the</strong> implementation effort for <strong>the</strong> original implementation from <strong>the</strong><br />

author [76] <strong>and</strong> compare <strong>the</strong> two implementations in Table 4.2. As can be observed,<br />

over a third <strong>of</strong> <strong>the</strong> original effort was for implementing support for a single file system<br />

driver. Fur<strong>the</strong>rmore, <strong>the</strong> time cited is only for <strong>the</strong> original implementation <strong>and</strong> does

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

Saved successfully!

Ooh no, something went wrong!