Search by property

From COMP15212 Wiki

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.

Search by property

A list of all pages that have property "Summary" with value "The schedule is the routine or algorithm which decides what to do next.". Since there have been only a few results, also nearby values are displayed.

Showing below up to 18 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


    

List of results

  • Shell Scripting  + (Some examples of jobs which can be done easily with simple ‘command line’ scripts.)
  • Bibliography  + (Some further reading in a more "conventional" form.)
  • Interprocess Communication  + (Some high-level notes on how two or more independent processes may communicate.)
  • Pointer Exercise  + (Some practice (for beginners in C) in how to get at memory 'directly'.)
  • Software Exceptions  + (Some processors will trap to the O.S. when the processor encounters an execution anomaly - e.g. division by zero.)
  • Errors  + (Some run time errors are unavoidable. They should still be considered and handled in a defined way.)
  • Operation Ordering  + (Sometimes the order in which operations are performed is vitally important - especially in a multi-threaded environment.)
  • Atomicity  + (Sometimes two (or more) operations need to be performed 'simultaneously'. Since software cannot do this there need to be mechanisms to ensure no outside operations interfere.)
  • Process Priority  + (Sometimes, some processes may be more important or urgent than others. Priority schemes can provide a greater share of resources (particularly processor time) for selected tasks. This can be particularly important in real-time systems.)
  • Introduction to Operating Systems  + (Start here! This links to the major, top-level concepts.)
  • Acknowledgements  + (Thanks to contributors to this site.)
  • Application Binary Interface (ABI)  + (The Application Binary Interface specifies the way software elements communicate within a program.)
  • Synchronisation  + (The act of collecting together disparate threads so all are at definitive points in their execution.)
  • Process States  + (The basic data behind <i>scheduling</i> processes.)
  • Kernel  + (The central, essential part of an operating system. Approaches vary.)
  • Context  + (The context is the state of a running process.)
  • Paging  + (The mechanism by which memory mapping is usually managed.)
  • Process Scheduling  + (The process of sharing the processor (or other) time amongst competing needs.)
  • Scheduler  + (The schedule is the routine or algorithm which decides what to do next.)
  • Virtual Memory  + (The separation of the user's view of memory and the physical reality on any given machine. Usually involves translating addresses and may employ paging from backing store.)
  • File Attributes  + (The sort of metadata which accompanies every file.)
  • File Descriptor  + (The system used to maintain an open file.)
  • Memory Segmentation  + (The way memory is organised into logically consistent areas.)
  • Filing System Implementation  + (There are many ways of constructing a file system, even if different mechanisms <i>look</i> the same to a user. Here are some examples.)
  • Peripheral devices  + (These are the <b>hardware</b> interfaces which provide the physical I/O for the computer. There may be a large variety in any given system.)
  • Structures  + (This article covers software collections of associated variables (usually with mixed <i>types</i>) as in a C ‘struct’ or the data in a Java object.)
  • About this resource  + (This describes the major features of this site.)
  • Threads  + (Threads are separate code sequences which can be executed in parallel. In general, one <i>process</i> can have several threads with the same memory context.)
  • Man(ual pages in Unix)  + (Unix on-line manual.)
  • Streams  + (Unstructured, serial data communications channels.)
  • Monitoring  + (Watching what is going on.)
  • File Types  + (What <i>sort</i> of thing is in this file?)
  • Idle  + (What a processor does when there's nothing better to do.)
  • Boot  + (What processes might run as a computer starts up?)
  • File Permissions  + (Who is allowed to do what to a file.)
  • Memory Fault  + (Why a memory transfer might fail and things which might be done about it.)