0% found this document useful (0 votes)
2 views

Lecture 3

The document outlines the various services provided by operating systems, including user interfaces, program execution, I/O operations, and file-system manipulation. It also discusses system calls as a programming interface for these services, detailing how parameters are passed to the OS and the relationship between APIs and system calls. Additionally, it highlights the importance of resource allocation, error detection, and security in ensuring efficient system operation.

Uploaded by

yushahabib25
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views

Lecture 3

The document outlines the various services provided by operating systems, including user interfaces, program execution, I/O operations, and file-system manipulation. It also discusses system calls as a programming interface for these services, detailing how parameters are passed to the OS and the relationship between APIs and system calls. Additionally, it highlights the importance of resource allocation, error detection, and security in ensuring efficient system operation.

Uploaded by

yushahabib25
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

OPERATING-SYSTEM

STRUCTURES
LECTURE 3
OPERATING SYSTEM SERVICES

One set of operating-system services provides functions that are


helpful to the user:
 User interface -Almost all operating systems have a user interface
(UI). Varies between Command-Line (CLI), Graphics User
Interface (GUI), Batch
 Program execution -The system must be able to load a program
into memory and to run that program, end execution, either
normally or abnormally (indicating error)
CONTINUE….

 I/O operations -A running program may require I/O, which may


involve a file or an I/O device.
 File-system manipulation -The file system is of particular interest.
Obviously, programs need to read and write files and directories,
create and delete them, search them, list file Information,
permission management.
OPERATING SYSTEM SERVICES (CONT.)

One set of operating-system services provides functions that are helpful


to the user (Cont):
 Communications –Processes may exchange information, on the same
computer or between computers over a network
 Communications may be via shared memory or through message
passing (packets moved by the OS)
 Error detection –OS needs to be constantly aware of possible errors
 May occur in the CPU and memory hardware, in I/O devices, in user
program
 For each type of error, OS should take the appropriate action to ensure
correct and consistent computing
 Debugging facilities can greatly enhance the user’s and programmer’s
abilities to efficiently use the system
OPERATING SYSTEM SERVICES (CONT.)

 Another set of OS functions exists for ensuring the efficient


operation of the system itself via resource sharing
 Resource allocation -When multiple users or multiple jobs
running concurrently, resources must be allocated to each of them
 Many types of resources -Some (such as CPU cycles, main
memory, and file storage) may have special allocation code, others
(such as I/O devices) may have general request and release code.
 Accounting -To keep track of which users use how much and what
kinds of computer resources
OPERATING SYSTEM SERVICES (CONT.)

 Protection and security -The owners of information stored in a


multiuser or networked computer system may want to control use
of that information, concurrent processes should not interfere
with each other
 Protection involves ensuring that all access to system resources is
controlled
 Security of the system from outsiders requires user
authentication, extends to defending external I/O devices from
invalid access attempts If a system is to be protected and secure,
precautions must be instituted throughout it. A chain is only as
strong as its weakest link.
SYSTEM CALLS
SYSTEM CALLS

 Programming interface to the services provided by the OS


 Typically written in a high-level language (C or C++)
 Mostly accessed by programs via a high-level Application Program
Interface (API)rather than direct system call use
EXAMPLE OF SYSTEM CALLS
System call sequence to copy the contents of one file to another file
EXAMPLE OF STANDARD API

 Consider the ReadFile() function


 API—a function for reading from a file
EXAMPLE OF STANDARD API (CONT..)

 A description of the parameters passed to ReadFile()


 HANDLE file—the file to be read
 LPVOID buffer—a buffer where the data will be read into and
written from
 DWORD bytesToRead—the number of bytes to be read into the
buffer
 LPDWORD bytesRead—the number of bytes read during the last
read
 LPOVERLAPPED ovl—indicates if overlapped I/O is being used
SYSTEM CALL IMPLEMENTATION

 Typically, a number associated with each system call


 System-call interface maintains a table indexed according to these
numbers „
 The system call interface invokes intended system call in OS
kernel and returns status of the system call and any return values
„The caller need know nothing about how the system call is
implemented
 Just needs to obey API and understand what OS will do as a result
call
 Most details of OS interface hidden from programmer by API
 Managed by run-time support library (set of functions built into
libraries included with compiler)
API –SYSTEM CALL SYSTEM CALL –OS RELATIONSHIP
STANDARD C LIBRARY EXAMPLE
C program invoking printf() library call, which calls write() system
call
SYSTEM CALL PARAMETER PASSING

 Often, more information is required than simply identity of desired


system call
 Exact type and amount of information vary according to OS and call
„Three general methods used to pass parameters to the OS
 Simplest: pass the parameters in registers. In some cases, may be
more parameters than registers
 Parameters stored in a block, or table, in memory, and address of
block passed as a parameter in a register This approach taken by
Linux and Solaris
 Parameters placed, or pushed, onto the stack by the program and
popped off the stack by the operating system
 Block and stack methods do not limit the number or length of
parameters being passed

You might also like