Scribd
Upload
19 views7 pages

PPT Notes

The document outlines a presentation on Chapter 11: Input Output Organization, detailing the roles of various presenters and their assigned slides. Key topics include I/O interfaces, the differences between I/O and memory buses, modes of data transfer such as programmed I/O and interrupt initiated I/O, and the concept of Direct Memory Access (DMA). Each presenter elaborates on their respective topics, providing insights into the functioning and management of I/O systems.

Uploaded by

7320charur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
19 views7 pages

PPT Notes

The document outlines a presentation on Chapter 11: Input Output Organization, detailing the roles of various presenters and their assigned slides. Key topics include I/O interfaces, the differences between I/O and memory buses, modes of data transfer such as programmed I/O and interrupt initiated I/O, and the concept of Direct Memory Access (DMA). Each presenter elaborates on their respective topics, providing insights into the functioning and management of I/O systems.

Uploaded by

7320charur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Slide Distribution

Charu: Slide no. 4-11


Suhani Kamboj: Slide no. 12-19
Diti Arora: Slide no. 20-24
Kamayani Mishra: Slide no. 25-30
Nitya Kapoor: Slide no, 30-35

Introduction
Diti: (slide 01)Good morning, everyone. Thank you for
being here today. We’re here to give a presentation on
Chapter 11 i.e., Input Output Organization, (slide 2)
which mainly explores I/O Interface, Modes of transfer
and Direct Memory Access. I would first like charu to
begin.

Charu: (slide 3) Good morning all, I am Charu and I will


be focusing on what is Input output interface? And, one
subtopic under it, I/O Bus and Memory Interface.
(opens slide 4)
I/O interface eases the transfer of information between
the internal storage i.e., CPU and Memory and the
external I/O devices i.e., peripherals.
It does so by bridging the communication gap b/w the
CPU and peripherals, addressing diffs in opt and data
handling.
(opens slide 5)
There are 4 key differences between the CPU and
peripherals..
First the signa conversion, since peripherals are electro
magnetic or electromechanical whereas CPUs are
electronic which makes signal conversion necessity.
Second, is the data transfer rate which is cz the
peripherals operate at a slower rate than the cpus, hence
requiring a synchronization mechanism
Third comes the data formats as peripherals have diff
data code than the cpu and memory.
Last the operating modes, each peripheral has a unique
operating mode which must be managed to avoid
interface with other devices.
(opens slide 6)
Interface units are the special hardware comp. that
supervise and synchronize I/O transfers b/w CPU and
Peripherals.
Device controllers is what each peripheral may have to
manage its specific operations to ensure efficient
communication and operation without interrupting the
overall system.
(opens slide 7)
Now we have the I/O Bus and Interface Modules
(opens slide 8)
What Is, I/O Bus?
It serves as the communication link between the
processor and various peripheral devices.
Each interface is equipped with its own interface unit to
facilitate the communication with the processor.
(opens slide 9)
Here we have a figure of the I/O Bus Connection
It consists of:
~a processor that sends instructions and receives data
via the I/O Bus
~Data lines that carry the actual info exchanged
~address lines that select specific peripheral device for
communication
~control lines which provide signals for managing data
transfer and operations.
~peripherals for eg: keyboard, display, printer,magnetic
disk and magnetic tape
~interface which is connected to every peripheral to
manage communication with the I/O Bus
(opens slide 10)
Input Output Commands are a set of Instructions that are
sent from the processor to the interface units of the
peripheral devices.
There are 4 types of commands:
~Control Commands(instruct peripherals to perform
specific actions)
~Status Commands(check and report the status of
peripheral devices)
~Data Output Commands(Transfers data from processor
to peripherals)
~Data Input Commands(Transfers data from peripherals
to processor)
(opens slide 11)
The difference between control commands and status
commands are:
Control commands are used to manage the operation of a
device whereas status commands are used to query the
current state or condition of a device.
Control Commands instruct the devices to perform
specific actions or change its state, status commands
provide info about the device’s operational status, error
conditions and readiness to perform tasks.
Now I would like Suhani to take over. Thank You

Suhani Kamboj: Good morning all, I am Suhani Kamboj


and I will be focusing on I/O versus Memory Bus and
Isolated versus Memory Mapped I/O/
(opens slide 12)
First we will discuss about the I/O versus Memory Bus
(opens slide 13)
Here we can observe the Diagram of an I/O Bus
(opens slide 14)
The processor should not only communicate with the I/O
but also the memory unit. Similar to the I/O Bus the
memory bus also contains data, address, and read/write
control lines.
There are 3 ways in which the I/O bus and Memory bus
can be connected.
either by using 2 separate buses one for the memory and
the other by the I/O, or using just 1 common bus but
having separate control lines or using both common bus
and common control lines.
(opens slide 15)
Employing two distinct buses for the connection each
dedicated to I/O Bus and Memory Bus respectively,
ensures independent pathways, hence minimizing
conflict between the two .
(opens slide 16)
Here using a common bus but having distinct control
lines for each I/O Bus and Memory Bus ensures an
approach to better resource sharing while maintaining
the control over distinct functions. Eg. Isolated I/O, I/O
mapped I/O
(opens slide 17)
Having a common bus with shared control lines simplifies
the overall design by reducing the no. of dedicated
control lines. Eg, Memory Mapped I/O
(opens slide 18)
Now talking about the Isolated I/O vs Memory Mapped I/O
(opens slide 19)
~In isolated I/O where memory and I/O have separate
address space, in a memory mapped io both have same
address spaces.
~All address can be used by memory in isolated I/O but
in the memory mapped I/O address can be used by both
memory and I/O
~In Isolated I/O we use separate control lines for
operations but use the same control lines in the memory
mapped I/O
~Isolated I/O is larger in size due to more buses whereas
the memory mapped i/o is smaller in size
~Isolated I/O is complex as separate logic is used to
control both whereas in the memory mapped I/O, simpler
logic is used as I/O is also treated as memory only.
I would like Diti to continue from hereby. Thankyou

Diti Arora:
Good morning everyone, I am diti arora and I would be
briefing you all about the Modes of transfer and the
Example of a programmed I/O.
(opens slide 20)
Beginning with the modes of transfer
(opens slide 21)
The data that is transfereed between the Cpu and the I/O
device may be handled in variety of modes, such as:
Programmed I/O, Interrupt Initiated I/O and DMA that is
direct memory access
(opens slide 22)
We will first talk about the programmed i/o and later on
discuss about the interrupt initiated i/o and DMA.
(opens slide 23)
Programmed I/o is the mode where all the data transfer
activity (i/o to memory and vice versa) takes place
through the cpu. It is done by executing a number of
instructions.
The figure here gives us a view of the interface via which
the I/O communicates with the CPU
(opens slide 24)
The steps for Programmed I/o are:
((READ STEPS FROM THE PPT))
Now I would like Kamayani to continue further thankyou!

Kamayani Mishra:
(opens slide 25)
Good morning all. I Kamayani Mishra would like to delve
into the topic Interrupt Initiated I/O
(opens slide 26)
Now what actually is Interrupt initiated I/O?
It is a concept that enables the efficient communication
between the cpu and peripherals.
It’s an alternative to the cpu constantly monitoring the
flag to the let the interface inform the comp when it is
ready to transfer data
It always plays a crucial role in the overall performance
and responsiveness of a computing system
An Interrupt initiated i/o has the benefits that: the cpu
can focus on other tasks since the interrupts are
leveraged, and it’ll only respond when a peripheral req.
attention
It also helps to optimize the cpu’s utilization, which leads
to improved overall sys performance and responsiveness
(opens slide 27)
Next we have the types of interrupts..
We have 2 types: non-vectored in which a fixed memory
is used for making the isr and all the devices use the
same isr hence making the sys simpler but less flexible
the other is vectored in which the interrupt vector
provided by the interrupting device contains- isr address
or a pointer to the memory location storing the isr
address- it offers better flexibility and faster responses
for multiple devices.
(opens slide 28)
There are 3 steps for an Interrupt Initiated I/O to work…
[read the slide]
(opens slide 29)
software consideration:
~data transfer: in it the data is transferred item by item
until it is complete. Actions like stopping tape or printing
characters may be triggered by control commands. Error
checking and other safeguards are often incorporated.
~Interrupt coiled transfer:i/o software issues commands
to peripherals to interrupt when ready for data transfer.
It is serviced by software handling the data transfer
~dma transfer: i/o software initiates a dma channel to
handle data transfer directly between the peripheral and
memory, freeing up the processor for other tasks
I would like Nitya to take it forward from here..thankyou

Nitya Kapoor:
(opens slide 30)
Good morning everyone, I nitya Kapoor would like to
explain about DMA i.e., direct memory access and a
subtopic under it that is, dma controller.
(opens slide 31)
(opens slide 32)
(opens slide 33)
(opens slide 34)
(opens slide 35)
(opens slide 36)
(opens slide 37)

You might also like