2KINDS OF MIRCOPROCESSOR operation, and then storing the

result.
IBM POWER Architecture Microprocessors: 4. Stored Program Concept:
• Examples: POWER9, used in IBM • Programs are stored in the
servers and supercomputers. computer's memory.
• Characteristics: • Instructions are treated as data and
• Commonly used in enterprise-level can be manipulated by other
servers and high-performance programs.
computing clusters. 5. Common Bus System:
Power Architecture Microprocessors: • Instructions and data share a
• Examples: Freescale/NXP PowerPC, used common communication pathway
in some gaming consoles and embedded or bus.
systems. • The bus is used for transferring
• Characteristics: both instructions and data between
• Historically used in a range of the memory and the CPU.
applications, including automotive, 6. Flexibility:
networking, and industrial. • Von Neumann architecture is
flexible, allowing for the easy
Von Neumann modification of programs and data.
• It supports a wide range of
The Von Neumann architecture is a computer applications and tasks.
architecture design that is named after the 7. Used in General-Purpose Computers:
mathematician and computer scientist John von • Commonly employed in general-
Neumann. It is one of the most common purpose computers, from personal
architectures used in the design of computers. The computers to servers.
key features of the Von Neumann architecture
include:

Von Neumann Architecture: Key Points

1. Single Memory Space:

• Both instructions and data are
stored in the same memory unit.
• This contrasts with the Harvard
architecture, where separate
memories are used for instructions
and data.
2. Sequential Execution:
• Instructions are processed one at a
time, in a sequential order.
• The CPU fetches an instruction,
decodes it, executes it, and then
moves on to the next instruction.
3. Fetch-Execute Cycle:
• The CPU follows a repetitive cycle
of fetching an instruction from
memory, decoding it to determine
the operation, executing the
 Harvard architecture • The program memory is typically
read-only during program
The Harvard architecture refers to a design that execution.
separates the storage and processing of 6. Commonly Used in Embedded Systems:
instructions and data. This architectural approach • Harvard architecture is often used
has distinct and separate memory spaces for in embedded systems,
program instructions and data, which allows the microcontrollers, and digital signal
CPU to fetch instructions and data processors (DSPs).
simultaneously. This is in contrast to the Von • Its advantages in terms of
Neumann architecture, where instructions and parallelism and performance make
data share the same memory space. it suitable for real-time
applications.
Harvard Architecture: Key Points 7. Reduced Risk of Bottlenecks:
• Because instructions and data can
1. Separate Memory Spaces: be accessed simultaneously, there's
• Harvard architecture uses separate a reduced risk of bottlenecks in the
memory spaces for instructions and instruction-fetching process.
data. 8. Complexity:
• There is a dedicated memory for • Implementing Harvard architecture
storing program instructions can be more complex than Von
(instruction memory) and another Neumann architecture due to the
for storing data (data memory). need for separate buses and
2. Parallel Access: memory units.
• Instructions and data can be
fetched simultaneously since they
reside in separate memory units.
• This parallel access can potentially
enhance performance, especially in
scenarios where simultaneous
fetching is beneficial.
3. Independent Buses:
• Harvard architecture often employs
separate buses for instruction and
data transfer.
• This separation allows for
concurrent data and instruction
fetches.
4. Parallel Processing:
• The separation of instruction and
data memory allows for parallel
processing, which can lead to
increased throughput and
performance.
5. Limited Modification of Programs at
Runtime:
• In traditional Harvard architecture,
modifying instructions at runtime
can be more challenging compared
to Von Neumann architecture.
 electronics, industrial machines,
KINDS OF OPERATING SYSTEM and automotive systems.
9. Multi-Processor OS:
1. Single-User, Single-Tasking OS: • Examples: Linux, Windows Server
• Examples: MS-DOS (Microsoft (Enterprise versions)
Disk Operating System), early • Manages systems with multiple
versions of Apple DOS processors or cores.
• These OS are designed to support 10.Batch Processing OS:
only one user and one task at a • Examples: IBM OS/360, z/OS
time. • Processes data in batches without
2. Single-User, Multi-Tasking OS: user interaction.
• Examples: Windows, MacOS 11.Time-Sharing OS:
(modern versions), Linux • Examples: Unix, Linux, Windows
• Allows a single user to run (with multi-user support)
multiple programs simultaneously. • Shares computing resources among
3. Multi-User OS: multiple users by dividing CPU
• Examples: UNIX, Linux, Windows time.
Server 12.Hybrid OS:
• Supports multiple users accessing • Examples: Windows (combines
the system at the same time. aspects of different types)
4. Real-Time OS: • Integrates features from different
• Examples: VxWorks, QNX, types of operating systems.
FreeRTOS
• Designed for real-time applications 13.Multi-Processing OS:
where tasks have specific time • Examples: Linux, Windows
constraints. (Server editions)
5. Distributed OS: • Optimized for systems with
• Examples: Amoeba, Plan 9 from multiple processors or cores,
Bell Labs allowing concurrent execution of
• Distributes computing tasks across processes.
multiple machines in a network. 14.Multi-Threading OS:
6. Network OS: • Examples: Solaris, Windows,
• Examples: Novell NetWare, Linux
Windows Server (with network • Supports multiple threads of
services) execution within a single process,
• Provides network services like file enabling concurrent execution and
and print sharing. improved performance.
7. Mobile OS: 15.Multi-User, Multi-Tasking OS:
• Examples: Android, iOS, Windows • Examples: Unix, Linux, Windows
Mobile Server
• Specifically designed for mobile • Allows multiple users to run
devices like smartphones and multiple tasks simultaneously,
tablets. commonly used in server
8. Embedded OS: environments.
• Examples: VxWorks, Embedded
Linux, FreeRTOS
• Used in embedded systems, such
as those found in consumer
16.Distributed Real-Time OS: 23.Automotive OS:
• Examples: RTLinux, VxWorks • Examples: Automotive Grade
• Combines real-time capabilities Linux (AGL), QNX
with distributed computing, • Designed for use in automotive
suitable for applications requiring systems, including infotainment,
both real-time responsiveness and navigation, and control systems.
distributed processing.
24.Serverless OS:
17.Mobile/Desktop Hybrid OS: • Examples: AWS Lambda, Azure
• Examples: Windows 10 (Windows Functions
Continuum), Samsung DeX • Focuses on executing functions or
• Offers a unified experience across code snippets in response to events
both mobile devices and traditional without the need for traditional
desktop environments. server management.
18.Live CD/USB OS:
• Examples: Ubuntu Live CD, 25.Cloud OS:
Knoppix Examples: Google Chrome OS, AWS Fire
• Allows users to run an operating OS
system directly from a CD or USB • Optimized for cloud computing
drive without installing it on the environments, emphasizing connectivity,
computer. security, and integration with cloud
19.Thin Client OS: services.
• Examples: Citrix XenDesktop,
Microsoft Windows Virtual
Desktop
• Designed for systems where most
of the processing occurs on a
server, and thin clients only handle
display and user input.
20.Network-Attached Storage (NAS) OS:
• Examples: FreeNAS,
OpenMediaVault
• Specialized OS for managing and
providing networked file storage
services.
21.Hypervisor OS:
• Examples: VMware ESXi,
Microsoft Hyper-V, KVM
• Enables the virtualization of
multiple operating systems on a
single physical machine.
22.Wearable OS:
• Examples: watchOS (Apple
Watch), Wear OS (for
smartwatches)
• Tailored for wearable devices,
emphasizing simplicity and energy
efficiency.