Smartphone Operating System (779883), страница 11
Текст из файла (страница 11)
In Unix, simpler is better.There are many examples of this design philosophy. Commands onUnix are quite simple and can be combined to build more complexcommands. Files on Unix are not structures in any way but are consideredonly as a sequence of bytes, to be interpreted by individual applications.• The kernel is a monolithic kernel. Any changes to kernel operations – such as the change in serial-port implementation – requires achange in kernel source code and a recompilation and reinstallationof the entire kernel.• Unix is multitasking and supports multithreading. It supports configurable policies regarding scheduling of processes.
Unix is a multi-usersystem, where multiple users can be accessing the same computerand sharing the resources.• Devices are implemented as files and access to devices is achieved byopening the file representation of a device. Devices can be ‘opened’by multiple users for reading and by only one user for writing.• Unix uses virtual memory and uses memory mapping to avoid userapplications from accessing memory from other applications.
Memorymapping automatically translates any memory reference into the areareserved for the process.• Unix supports many kinds of file systems and communication methods through implementations of dynamically loaded implementationmodules and device drivers.Linux is an open-source version of Unix. The fact that Linux is opensource has been both a blessing and a curse: allowing the source code tothe operating system to be shared has fostered much innovation but hasalso allowed people to exploit weaknesses.42THE CHARACTER OF OPERATING SYSTEMSSymbian OSSymbian OS is unique among operating systems in the sense that it wasdesigned from its inception3 with smartphones as the target platform. Itis not a generic operating system shoehorned into a smartphone nor isit an adaptation of a larger operating system for a smaller platform.
Aswe saw in Chapter 1, Symbian OS has a history of evolving design (fromSIBO to EPOC to Symbian OS) specifically targeted at smartphones for itsimplementation.The precursors to Symbian OS have given their best features. Theoperating system is object-oriented, inherited from EPOC.
This meansthat systems calls involve system, or kernel-side, objects and that theidea of abstraction permeates system design. Where an operating systemsuch as Unix might create a file descriptor and use that descriptor as aparameter in an open call, Symbian OS would create an object of theRFile class and call the open() method tied to the object. In Unix, itis widely known that file descriptors are integers that index a table in theoperating system’s memory.
In Symbian OS, one really has no idea howthe file object is implemented; one simply creates an RFile object anduses its methods.Symbian OS has other inherited features. It is a multitasking andmultithreaded operating system. Many processes can run concurrently,they can communicate with each other and utilize multiple threads thatrun internal to each process.
The operating system has a file systemcompatible with Microsoft Windows (technically, a FAT32 file system); itsupports other file-system implementations through a plug-in interface. Ituses TCP/IP networking as well as several other communication interfaces,such as serial, infrared and Bluetooth.Symbian OS has some unique features that come from its focus onthe smartphone platform.
Because of limited (or, in most cases, no) diskstorage, no virtual memory is implemented. Symbian OS has a pluggablemessaging architecture – one where new message types can be inventedand implemented by developing modules that are dynamically loaded bythe messaging server.Consider the way system calls work in Symbian OS.
There are two typesof system call. An executive call makes a request for the kernel to execute3Note that the origins of Symbian OS can be found in EPOC (as stated in Chapter 1) andEPOC was not designed for smartphones. However, when Symbian OS was designed as areplacement for EPOC, it was indeed intended for smartphones and was designed with thistarget platform in mind.SUMMARY43an operation in privileged mode on behalf of the user-space requestor. Anexecutive call causes a software interrupt, which is serviced by branchingthe operation into kernel code. The interrupt is serviced and control ispassed back to the user. Executive calls can modify kernel-space objectsbut cannot create or delete them.
Operations such as memory allocationor thread creation need to be done by kernel-server requests. There isa server that protects kernel resources and requests to manipulate thoseresources need to go through that server. Server requests are themselvesexecutive calls.• The kernel structure of Symbian OS has a microkernel design. Minimalsystem functions and data are in the kernel with many system functionsspread out into user-space servers.
The servers get their jobs done bymaking executive calls into the kernel when necessary.• Symbian OS supports the use of virtual machines: the implementationof a ‘computer within a computer’. The implementation of the Javaprogramming language and the run-time environment needed to runJava is done through this mechanism.• Communication structures in Symbian OS are easily extended. Modules can be written to implement anything from user-level interfacesto new protocol implementations to new device drivers. Because ofthe microkernel design, these new modules can be introduced andloaded into the operation of the system dynamically.• Symbian OS has been designed at its core with APIs specialized formultimedia.
Multimedia devices and content are handled by specialservers and by a framework that lets the user implement modules thatdescribe new and existing content and what to do with it.2.4 SummaryThis chapter has been about the concepts and structures that make up thecharacter of an operating system.
Operating systems evolve over time asthe hardware they run on and the needs of users evolve.We discussed several concepts that are implemented in operatingsystems. We looked at system structures, including kernels, the interruptsystem and how applications become processes running on a CPU. Welooked at the different kinds of device I/O and how interrupts are used to44THE CHARACTER OF OPERATING SYSTEMSimplement them. We had an overview of storage structures, including thestorage hierarchy and the ideas involved in caching and file systems. Welooked at system protection strategies, from protection modes to waysof protecting memory and CPU usage.
We reviewed communicationstructures, implemented by sockets.The chapter concluded by taking examples of operating system character: we looked at IBM OS/360, Unix and Symbian OS.The next chapter begins our closer look at these operating systemcomponents by looking at processes and scheduling.Exercises1.Consider the following services and classify them as taking place inthe kernel or outside the kernel. Do this for both microkernel andhybrid kernel systems.a.
Opening and closing filesb. Writing to a registerc. Reading a memory celld. Receiving a text messagee. Playing a sound bite.2.Software interrupts are useful for many things. We discussed timersas an example of software interrupts. Think of other examples ina computer system of software interrupts. (Hint: Think of softwareinterrupts as events.)3.With software interrupts, what form does the interrupt vector take?Where is it stored?4.Context-switching is expensive because of the ‘context’ that isswitched. Try to identify as many parts of this context as you can.5.Often people think of ‘protection’ as ‘security’. We discussed waysto protect user programs and the operating system from each other.In what ways could the protection mechanisms we discussed be aform of security?6.We gave a few examples of device I/O types.
Can you developmore examples for each I/O type? Explain your answers.EXERCISES7.45Which of the following operations should be done in the kernel asprivileged mode?a. Reading and writing filesb. Sending a text messagec. Taking a picture with the camerad. Notifying a program about data receivede. Switching processes on the CPUf. Reading from a memory cell.8.What would a system look like without a privileged mode? Couldsuch an operating system be useful? How would it be possible toimplement protection?9.Systems typically have multiple caches built into the hardware; wecalled them L1 and L2. Why is multilevel caching useful?10.Survey the concepts and structures we discussed in this chapter.In what ways would hardware be useful to help implement aspecific structure? For example, how could hardware help withcontext-switching or memory protection?11.How would you classify a kernel that implemented the variousforms of the OS/360 operating systems?12.As we discussed, Symbian OS uses two levels of kernel spaceoperations: the executive call and the kernel-server request.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
