Kernel: Paggiddiatan a nagbaetan dagiti rebision
Content deleted Content added
Joemaza (tungtungan | aramid) No edit summary |
Joemaza (tungtungan | aramid) No edit summary |
||
Linia 2:
No dadduma a kita ti kernal ket agsabalida iti pamuspusan kadagiti pannakaaramid, ngem agdepende iti daremdemda ken pannakaaramatda. Dagiti [[sibubukel a kernel]] (monolithic kernel) ket ar-aramatenda dagitoy pagtungpalan babaen ti pannakapataray iti kodigo iti uneg ti pareho nga lugar ti pagtaengan ti memoria (memory address space) tapno masaysayaatan ti pannakaaramid ti sistema. Ngem, dagiti [[nakabasbassit a kernel]] (microkernel) ket pinapatarayda dagiti kaaduan a panagserbida (services) iti uneg ti lugar ti mangaramat (user space). Ti pagtungpalanda ket pannakalaing ti pannaripato ken ti sebangan ti base ti kodigo.
<!--
==Overview==
Most, but not all, operating systems rely on the kernel concept. The existence of a kernel as a single piece of software responsible for the communication between the hardware and the software results from complex compromises relating to questions of performance, memory efficiency, security and [[CPU design|processor architectures]].
In most cases, the [[boot loader]] starts executing the kernel in [[supervisor mode]],<ref name="supervisor">The highest privilege level has various names throughout different architectures, such as supervisor mode, kernel mode, CPL0, DPL0, Ring 0, etc. See [[Ring (computer security)]] for more information.</ref> The kernel then initializes itself and starts the first process. After this, the kernel does not typically execute directly, only in response to external events (e.g. via system calls used by applications to request services from the kernel, or via interrupts used by the hardware to notify the kernel of events). Additionally, the kernel typically provides a loop that is executed whenever no processes are available to run; this is often called the ''idle process''.
Kernel development is considered one of the most complex and difficult tasks in programming.<ref name="bkerndev">[http://osdever.net/bkerndev/index.php?the_id=90 Bona Fide OS Development - Bran's Kernel Development Tutorial], by Brandon Friesen</ref> Its central position in an operating system implies the necessity for good performance, which defines the kernel as a critical piece of software and makes its correct design and implementation difficult. For various reasons, a kernel might not even be able to use the [[Abstraction (computer science)|abstraction]] mechanisms it provides to other software. Such reasons include [[memory management]] concerns (for example, a user-mode function might rely on memory being subject to [[demand paging]], but as the kernel itself provides that facility it cannot use it, because then it might not remain in memory to provide that facility) and lack of [[Reentrant|reentrancy]], thus making its development even more difficult for software engineers.
A summary of basic kernel functions includes: low-level scheduling of processes ([[dispatching]]), [[Inter-process communication]], process [[Synchronization (computer science)|synchronization]], [[context switch]], manipulation of [[process control block]]s, [[interrupt]] handling, process creation and destruction, process suspension and resumption (see [[process states]])<ref name="Deitel82KernelFunctions">Deitel 82, p.65-66 cap. 3.9</ref>.
-->
{{stub}}
| |||