Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

Containers + (A contemporary mechanism for implementing virtual machines.)

Memory Leak + (A fault whereby memory - a valuable resource - is claimed and then forgotten about, thus, typically, causing an application to request more and more of this resource.)
Network File System (NFS) + (A file system can use different storage 'devices' including remote, networked machines.)
Filing System + (A filing system is a place to keep all the information the computer may want but is not in current use. It can involve a variety of both software and hardware technologies.)
Dirty Bit + (A flag indicating that a cache has been modified and (temporarily) holds the definitive copy of some data.)
Resources + (A general heading for the various facilities - memory, time, I/O devices etc. - which a computer has. An OS typically tries to allocate and ration these to provide the best overall performance, often amongst many concurrent processes.)
Signal and Wait + (A generic approach to access control to ‘sensitive’ code sections. A process must wait its turn and signal others when it is finished.)
Interrupt Controller + (A hardware device used to assist the rapid dispatch to an appropriate interrupt service routine.)
Disk Partition + (A logical (rather than physical) division of some backing store.)
Journalling File System + (A means of increasing the robustness of a filing system. Akin to version control, for files.)
Emulator traps + (A means of using software to substitute for 'missing' processor hardware. An example is the use of a model of a floating point unit when a particular chip doesn't contain that hardware unit.)
Direct Memory Access (DMA) + (A mechanism to move data in/out/around memory without software intervention.)
Memory Mapping Extra + (A more detailed look towards practical memory mapping.;)
Arrays + (A note about programming arrays in C.)
Write Buffer + (A place to queue up (slow) output operations to avoid having to wait for them to complete.)
Memory Sizes + (A pragmatic look at the organisation of memory. Some terminology with which every computer scientist ought to be familiar.)
Interrupt Service Routines (ISRs) + (A procedure (or “method”) called by the hardware 'behind the scenes'. User applications are not directly aware of these.)
Dynamic Memory Allocation + (A process wants more memory; the OS tries to provide it.)
Race Conditions + (A race condition is normally a mistake, where two (or more) operations can complete in different orders - and thus leave different results - depending on issues such as the way threads are scheduled.)
Semaphores + (A signalling mechanism for access control in processes.)
Exercises + (A summary page for the various practical exercises for this module.)
Watchdog + (A system to facilitate crash recovery in embedded systems.)
Queues + (A widely used principle in operating systems (and elsewhere). Includes a look at implementation techniques.)
Memory Mapping Example + (A worked memory mapping example.)
Virtualisation + (An abstraction of some physical resource, typically for providing regularity in an interface or transparent sharing of the resource.)
Sockets + (An abstracted endpoint of a communications path.)
Synchronisation Barrier + (An animated demonstration of a synchronisation barrier.)
Timers + (An example I/O peripheral.)
I-nodes + (An example of filing system implementation)
FAT + (An example of filing system implementation.)
Paging States + (An example to help explain paging.)
Reset + (An exception which restarts the processor or system.)
Unix proc Exercise + (An exploration of some of the Unix internal data made human readable and pretending to be files.)
Security + (An important, all-spanning topic in comput … An important, all-spanning topic in computing. Within an operating system the primary concerns are to ensure that application processes can affect neither each other nor the operating system itself. This should include any leakage of illicit information.nclude any leakage of illicit information.)
Interrupts + (An interrupt is a form of exception where the hardware calls for a software service.)
What is an OS + (An operating system is a layer of software which lies between the application(s) program(s) and the hardware.)