• Summary
• Related Documents
  • Active Bibliography
  • Co-citation
• Version History

Popular Tags

Add a tag:

No tags have been applied to this document.

BibTeX | Add To MetaCart

@INPROCEEDINGS{Liedtke96µ-kernelsmust,
    author = {Jochen Liedtke},
    title = {µ-Kernels Must And Can Be Small},
    booktitle = {In 5th International Workshop on Object Orientation in Operating Systems (IWOOOS},
    year = {1996},
    pages = {152--155},
    publisher = {IEEE}
}

Bookmarks

         

OpenURL

 

Abstract:

For a general acceptance, -kernels must be fast and not burden applications. For fulfilling these conditions, cache architectures require -kernels to be small. The L4 -kernel shows that smallness can be achieved. 1. -kernels must be small This is not obvious. Most first-generation -kernels were large; typically they need 300 Kbyte of code and 140 system calls. Some of their architects argued that `' in this context means `lower level' and not `small size'. Demanding smallness radically differs from this approach. It could (and in fact it does) change -kernel technology dramatically. Why should -kernels be as small as possible? (We avoid the term "minimal" because of its mathematical implications.) The reasons are performance, flexibility and perhaps correctness. 1.1. "A non-small -kernel is not fast." The most relevant performance costs of a -kernel result from its cache consumption. If a frequently invoked kernel operation accesses a substantial part of the primary cache ("floods...

Citations