"... In PAGE 115: ...2 Normalized performance relative to Linux L4Linux w/spine L4Linux Linux Figure 25: SPEC CPU 2000 benchmarks comparing Linux, L4Linux, and spine dynamic control ow graph can be assessed. Figure 25, Table 9, and Table10 show performance results of the spine architecture as compared to the normal L4Linux system and the stock Linux kernel. The SPEC CPU 2000 benchmarks show virtually no di erence in performance.... In PAGE 115: ... The spine column shows a performance penalty near 30% relative to L4Linux but has a worst case of a 74% increase in penalty. The lmbench results show a signi cant performance penalty as compared to Linux, however the Linux kernel compile time benchmark in Table10 provides a better approximation of how the overal system will be penalized. Table 10 shows a performance penalty of about 34% for the spine system as compared to Linux system.... In PAGE 115: ... The lmbench results show a signi cant performance penalty as compared to Linux, however the Linux kernel compile time benchmark in Table 10 provides a better approximation of how the overal system will be penalized. Table10 shows a performance penalty of about 34% for the spine system as compared to Linux system. It should be noted that the implementation of spine is not optimized.... ..."

"... In PAGE 5: ...bout 1.6 MLOCs. The core kernel and file systems contain 12 KLOCs and 235 KLOCs, respectively. Table1 , which is an updated version of the one published in Ref. [24], shows the most important events in the Linux kernel development time table, along with the number of releases produced for each development series.... ..."

"... In PAGE 6: ... On the other hand, the monolithic and KLASY kernels are statically linked and thus they should have performance advantages. Table2 lists the index numbers reported by the benchmark programs. A larger number is better.... ..."

"... In PAGE 7: ... 5.2 Evaluation We have evaluated our system with 18 real-world kernel-level rootk- its ( Table1 ) that are publicly available. Note that all of these rootk- its can successfully compromise the OS kernel integrity on vulner-... In PAGE 7: ... The detailed examinations are helpful to understand how our system is able to effectively detect and prevent kernel integrity violations. As shown in Table1 , the adore rootkit makes use of the loadable ker- nel module (LKM) support in commodity Linux kernels to directly hijack a number of system call table entries. The adore-ng rootkit uses the same LKM support to subtly modify the jump table of the virtual file system.... ..."

"... In PAGE 6: ...he module level. We also ignored common coupling of constants. In this way we determined the number of instances of common coupling between each kernel module and all the other modules in each version of Linux. Data for six successive versions of three kernel modules are shown in Table2 , and also in Figure 1, which displays the data of Table 2 in graphical form. A blank in the date column denotes that the code has not changed between successive versions.... In PAGE 6: ...he module level. We also ignored common coupling of constants. In this way we determined the number of instances of common coupling between each kernel module and all the other modules in each version of Linux. Data for six successive versions of three kernel modules are shown in Table 2, and also in Figure 1, which displays the data of Table2 in graphical form. A blank in the date column denotes that the code has not changed between successive versions.... In PAGE 6: ....1.104 of Linux. As can be seen in the second column of Table2 , the number of instances of common coupling then steadily increased to 946 in version 2.1.... In PAGE 7: ... Page 7 Figure 1 shows that, even when the code is unchanged, the number of instances of common coupling can progressively increase. [Figure 1 should go here] [ Table2 should go here] 4. Results Details of the 6499 kernel modules appear in Table 3.... In PAGE 17: ... Growth in the size of Linux. Table2 . Data for six successive versions of three Linux kernel modules.... ..."

"... In PAGE 12: ... 5.2 Locking and Source Code Changes Table2 shows the how the lock usage has evolved throughout the Linux development. The table shows the number of places in the kernel where locks are acquired and released.... ..."