XNU

From Free net encyclopedia

XNU is the name of the kernel that Apple developed for use in the Mac OS X operating system and released as open source as part of the Darwin operating system. It is a hybrid kernel combining the Mach kernel version 3.0, developed at Carnegie Mellon University with components from the FreeBSD 5.X kernel as well as a [[C++]] API for writing drivers called I/O Kit. XNU is an acronym for X is Not Unix.Template:Ref

1 Kernel design
2 Protecting shared resources
3 Supported processors
4 References
5 External links

[edit]

Kernel design

Like some other modern kernels, XNU is a hybrid, containing features of both monolithic and microkernels, attempting to make the best use of both technologies, such as the message passing capability of microkernels enabling larger portions of the OS to benefit from protected memory, as well as retaining the speed of monolithic kernels for certain critical tasks.

Mach was originally conceived as a simple, extensible microkernel. As such, it is able to run the core of an operating system as a separated process, which allows a great flexibility (one could run several operating systems in parallel above the Mach core), but this reduces performance because of the translations between Mach and the different codebases. With Mac OS X, since the behavior of the system is known in advance, BSD functionalities were built into the core with Mach. The result is a combination of the assets of Mach and BSD.

[edit]

Mach

The core of the XNU kernel, Mach, provides kernel threads, processes, pre-emptive multitasking, message-passing (used in inter-process communication), protected memory, virtual memory management, very soft real-time support, kernel debugging support, and console I/O. The Mach component also allows the OS to host binaries for multiple distinct CPU architectures within a single file (such as x86 and PowerPC) due to its use of the Mach-O binary format.

[edit]

BSD

The BSD portion of the kernel provides the POSIX API (BSD system calls), the Unix process model atop Mach tasks, basic security policies, user and group ids, permissions, the network stack, the virtual file system code (including a filesystem independent journalling layer), cryptographic framework, System V IPC, and some of the locking primitives.

[edit]

I/O Kit

This is the device driver framework, written in a subset of [[C++]]. Due to its object-oriented design, device drivers can be written more quickly while using less code; features common to any class of driver are provided within the framework itself. The I/O Kit is multi-threaded, SMP safe, and allows for hot pluggable devices and automatic, dynamic device configuration.

Many drivers can be written to run from user-space, which further enhances the stability of the system; if a user-space driver crashes, it will not crash the kernel.

[edit]

Protecting shared resources

In order to run safely on multiprocessor machines, access to shared resources (files, data structures etc.) must be serialized so that threads or processes do not attempt to modify the same resource at the same time. Atomic operations, spinlocks, critical sections, mutexes, and serializing tokens are all possible methods that can be used to prevent concurrent access. Like both Linux and FreeBSD 5, XNU, as of Mac OS X 10.4 and Darwin 8.0, employs a fine-grained mutex model to achieve higher performance on multiprocessor systems.

[edit]