カーネル

ウィキペディア

索引トップ用語の索引ランキングカテゴリー

出典: フリー百科事典『ウィキペディア（Wikipedia）』 (2023/09/23 03:13 UTC 版)

外部リンク

Detailed comparison between most popular operating system kernels

脚注

注釈

^ ^a ^b 最上位の特権レベルは、スーパーバイザーモード、カーネルモード、CPL0、リング0など様々な呼称がある。
^ CPU時間は理論上無限だが、メモリ容量とそのアクセス速度は有限であることに注意すべきである。
^ デバイスドライバをカーネルの一部とみなさない考え方もあるが、たとえばリアルタイムクロックなどはカーネル自身が管理する。
^ 仮想アドレッシングは通常、メモリ管理ユニット (MMU) に内蔵された機能を使用して実現される。
^ そもそも何故カーネルが大きくなるとまずいのか？一般にOSはある程度のハードウェアシリーズで動作するが、その最小メモリサイズは最も安価なハードウェアの最小構成まで考慮する必要があり、そのようなメモリ容量でもある程度の機能が動作しなければならない。このため、少なくとも一般的な構成のカーネルがその最小メモリ容量内に収まって、アプリケーションをそれなりの性能で実行できるだけの空きメモリ容量を確保しなければならないという事情があった。最近ではメモリチップの急速な大容量化によって、このような問題は減りつつある。

出典

^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ Wulf 1974, pp. 337–345
^ ^a ^b An overview of Monolithic and Micro Kernels, by K.J.
^ Roch 2004
^ Bona Fide OS Development - Bran's Kernel Development Tutorial, by Brandon Friesen
^ Levy 1984, p. 5
^ Needham, R.M., Wilkes, M. V. Domains of protection and the management of processes, Computer Journal, vol. 17, no. 2, May 1974, pp 117–120.
^ ^a ^b ^c Silberschatz 1991
^ http://www.answers.com/topic/operating-system
^ Tanenbaum, Andrew S. (2008). Modern Operating Systems (3rd ed.). Prentice Hall. pp. 50–51. ISBN 0-13-600663-9. ". . . nearly all system calls [are] invoked from C programs by calling a library procedure . . . The library procedure . . . executes a TRAP instruction to switch from user mode to kernel mode and start execution . . ."
^ Denning 1976
^ Swift 2005, p. 29 quote: "isolation, resource control, decision verification (checking), and error recovery."
^ Schroeder 1972
^ ^a ^b Linden 1976
^ Stephane Eranian and David Mosberger, Virtual Memory in the IA-64 Linux Kernel, Prentice Hall PTR, 2002
^ Silberschatz 1993, pp. 445, 446
^ Hoch, Charles; J. C. Browne (University of Texas, Austin) (July 1980). “An implementation of capabilities on the PDP-11/45” (PDF). ACM SIGOPS Operating Systems Review 14 (3): 22–32. doi:10.1145/850697.850701 2007年1月7日閲覧。.
^ ^a ^b A Language-Based Approach to Security, Schneider F., Morrissett G. (Cornell University) and Harper R. (Carnegie Mellon University)
^ ^a ^b ^c P. A. Loscocco, S. D. Smalley, P. A. Muckelbauer, R. C. Taylor, S. J. Turner, and J. F. Farrell. The Inevitability of Failure: The Flawed Assumption of Security in Modern Computing Environments. In Proceedings of the 21st National Information Systems Security Conference, pages 303–314, Oct. 1998.
^ J. Lepreau et al. The Persistent Relevance of the Local Operating System to Global Applications. Proceedings of the 7th ACM SIGOPS European workshop, 1996.
^ J. Anderson, Computer Security Technology Planning Study, Air Force Elect. Systems Div., ESD-TR-73-51, October 1972.
^ Jerry H. Saltzer, Mike D. Schroeder (September 1975). “The protection of information in computer systems”. Proceedings of the IEEE 63 (9): 1278–1308. doi:10.1109/PROC.1975.9939.
^ Jonathan S. Shapiro; Jonathan M. Smith; David J. Farber (1999). “EROS: a fast capability system”. Proceedings of the seventeenth ACM symposium on Operating systems principles 33 (5): 170–185. doi:10.1145/319344.319163.
^ Dijkstra, E. W. Cooperating Sequential Processes. Math. Dep., Technological U., Eindhoven, Sept. 1965.
^ ^a ^b ^c ^d ^e ^f Hansen 1970, pp. 238–241
^ “SHARER, a time sharing system for the CDC 6600”. 2007年1月7日閲覧。
^ “Dynamic Supervisors – their design and construction”. 2007年1月7日閲覧。
^ Baiardi 1988
^ ^a ^b Levin 1975
^ Denning 1980
^ Jürgen Nehmer The Immortality of Operating Systems, or: Is Research in Operating Systems still Justified? Lecture Notes In Computer Science; Vol. 563. Proceedings of the International Workshop on Operating Systems of the 90s and Beyond. pp. 77–83 (1991) ISBN 3-540-54987-0 [1] quote: "The past 25 years have shown that research on operating system architecture had a minor effect on existing main stream systems." [2]
^ Levy 1984, p. 1 quote: "Although the complexity of computer applications increases yearly, the underlying hardware architecture for applications has remained unchanged for decades."
^ ^a ^b ^c Levy 1984, p. 1 quote: "Conventional architectures support a single privileged mode of operation. This structure leads to monolithic design; any module needing protection must be part of the single operating system kernel. If, instead, any module could execute within a protected domain, systems could be built as a collection of independent modules extensible by any user."
^ Open Sources: Voices from the Open Source Revolution
^ Linus vs. Tanenbaum や LINUX is obsolete - comp.os.minix や Appendix A The Tanenbaum-Torvalds Debate に議論の記録がある
^ ^a ^b Matthew Russell. “What Is Darwin (and How It Powers Mac OS X)”. O'Reilly Media. 2012年9月30日閲覧。 quote: "The tightly coupled nature of a monolithic kernel allows it to make very efficient use of the underlying hardware [...] Microkernels, on the other hand, run a lot more of the core processes in userland. [...] Unfortunately, these benefits come at the cost of the microkernel having to pass a lot of information in and out of the kernel space through a process known as a context switch. Context switches introduce considerable overhead and therefore result in a performance penalty."
^ ^a ^b ^c ^d ^e ^f ^g Liedtke 1995
^ Härtig 1997
^ Hansen 1973, section 7.3 p.233 "interactions between different levels of protection require transmission of messages by value"
^ ^a ^b The L4 microkernel family – Overview
^ KeyKOS Nanokernel Architecture
^ Ball 2002, p. 129
^ Hansen 2001, pp. 17–18
^ BSTJ version of C.ACM Unix paper
^ Introduction and Overview of the Multics System, by F. J. Corbató and V. A. Vissotsky.
^ ^a ^b The UNIX System — The Single Unix Specification
^ Unix’s Revenge by Horace Dediu
^ Linux Kernel 2.6: It's Worth More!, by David A. Wheeler, 2004年10月12日。
^ XNU: The Kernel
^ Windows History: Windows Desktop Products History
^ The Fiasco microkernel - Overview
^ L4Ka - The L4 microkernel family and friends
^ QNX Realtime Operating System Overview