CONTROL UNIT
Micro-programmed and Hardwired
Full of definitions
and theory to learn.
LINK:CONTOL UNIT (11 mb)
REGISTER AND STACK ORGANIZATION
Processor organisaiton
Important questions.
Reverse polish
notation.
Stack organization(
simple and easy topic must come in exams)
ADDRESSING MODES
(This topic is important)
INSTRUCTION FORMAT
1 address instruction, 2 address instruction, 3 address instruction, zero address instruction
RISC, instruction format.
DATA TRANSFER INSTRUCTION &
PROGRAM CONTROL INSTRUCTIONS
I/O ORGANIZATION
Modes of transfer, direct memory access, serial communication, DMA controller.
PROCESSOR AND INTERUPTS
CACHE MEMORY
MAIN MEMORY
RAM chip ,ROM chip,
Memory Address Map,
Auxiliary Memory
VIRTUAL MEMORY
Page Replacement algorithm.
INT HANDLING AND PERIPHERAL DEVICES
LNIK:DOWNLOAD LINK
LINK FOR LAST POST IN WHICH I HAD COVERED MORE TOPIC FOR COMPUTER ORGANIZATION
COMPUTER ORGANIZATION
It’s about the design of different hardware computer parts and how they come together to form a computer system. Typically this type of class is split into 2 major parts: CPU design and cache/memory design.
Specific examples of common topics taught in this type of course include: boolean circuits and logic (ie ALUs, muxes, etc), processor pipeline design and features (ie pipelining, forwarding), assembly language programming, memory hierarchy, cache design, cache coherence, and virtual memory.
Advanced classes may teach concepts such as advanced pipeline design (ie register renaming, superscalar architectures), instruction level parallelism, multiprocessor parallelism protocols, and advanced cache design.
Even if you’re not interesting in hardware design/computer architecture this class will give you a fundamental understanding of what a computer is and how it works which is vital to optimizing higher level code. It will also introduce you to problem-solving methods that are thematic throughout computer science such as parallelism and abstraction.
Computer Organization, as the name suggests, is all about how the various parts of a computer are organized.
As a subject in CSE, it should be dealing with major architectural components of a general computing machine and how these components are organized, interconnected and working together. It essentially talks about the various components such as processor, memory, IO devices, storage devices, interconnection methods, operating modes, communication between components, the hierarchy of how these components are organized etc
After learning this subject, one should get a fair idea of how the varied components work in tandem to give the user an experience of a single whole machine, rather than that of multiple connected parts.
Dont get caught in measuring "best" approaches to learn computer architecture. Best is usually subjective. Look for learning approaches that are comfortable, fundamental and challenging.
I am learning computer architecture since many years. I have used text books, lecture slides, lecture videos, research articles, expert talks, blogs, news, processor manuals, circuit board manuals, software/ hardware study objects and prototyping. Its a lot of work and despite using many sources, I still feel there is a lot I dont know.
Among the approaches I have used, the most effective one was prototyping. Like others have suggested, build something computer architecture like.
I dont recommend building an OS, its a daunting task and it penetrates computer architecture concepts superficially.
Instead, build a compiler middle-end and backend (keywords: VLIW, vectorization, loop optimizations). Another good way is to build your own or modify an existing simulator (keywords: gem5, simple - scalar, MARS). Perhaps you can describe your favorite computer architecture using a hardware description language (keywords: VHDL, Chisel) and synthesize the design on a FPGA? The idea in simple - get your hands dirty with prototyping and persist until you understand deeply.
In terms of books, apart from H&P Computer Architecture, I strongly recommend Morgan Kaufmanns book series Synthesis Lectures on Computer Architecture. These books are like gold mines- they are well written, deep, focused and convey essential concepts memorably.
I am learning computer architecture since many years. I have used text books, lecture slides, lecture videos, research articles, expert talks, blogs, news, processor manuals, circuit board manuals, software/ hardware study objects and prototyping. Its a lot of work and despite using many sources, I still feel there is a lot I dont know.
Among the approaches I have used, the most effective one was prototyping. Like others have suggested, build something computer architecture like.
I dont recommend building an OS, its a daunting task and it penetrates computer architecture concepts superficially.
Instead, build a compiler middle-end and backend (keywords: VLIW, vectorization, loop optimizations). Another good way is to build your own or modify an existing simulator (keywords: gem5, simple - scalar, MARS). Perhaps you can describe your favorite computer architecture using a hardware description language (keywords: VHDL, Chisel) and synthesize the design on a FPGA? The idea in simple - get your hands dirty with prototyping and persist until you understand deeply.
In terms of books, apart from H&P Computer Architecture, I strongly recommend Morgan Kaufmanns book series Synthesis Lectures on Computer Architecture. These books are like gold mines- they are well written, deep, focused and convey essential concepts memorably.
Tags:
Coder's Life