Basic Computer Architecture and Quantitative Techniques in Computer Design Instruction Pipeline ,Arithmetic Pipeline, Hazards ,Exception and Interrupts

We talk about the quantitative approach to computer architecture in this paper. We also go over Amdahl's Law, scalability, parallelism, and the principle of locality in relation to quantitative measurement. We also demystify computer architecture by focusing on smart technical design and cost-...

Full description

Saved in:
Bibliographic Details
Published inINTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT Vol. 8; no. 3; pp. 1 - 13
Main Author Sardar, Rupam
Format Journal Article
LanguageEnglish
Published 07.03.2024
Online AccessGet full text
ISSN2582-3930
2582-3930
DOI10.55041/IJSREM29101

Cover

More Information
Summary:We talk about the quantitative approach to computer architecture in this paper. We also go over Amdahl's Law, scalability, parallelism, and the principle of locality in relation to quantitative measurement. We also demystify computer architecture by focusing on smart technical design and cost- performance-power trade-offs. In the context of computer architecture, we think the field has continued to develop and move toward the exacting quantitative foundation of venerable scientific and technical disciplines. The pipelining principles in processor design are the focus of this study.The fundamentals of the instruction pipeline are covered, and an example-based explanation of how to reduce a pipeline delay is provided.The primary goal is to comprehend how a processor's pipeline functions.The different risks that lead to pipeline deterioration are described, along with ways to reduce them. Architecture-based development environments are emerging as a useful tool for building reliable distributed systems. By means of the abstract characterization of intricate software Software reuse and evolution are encouraged in terms of system topologies that involve the interface- level interaction of software parts. Furthermore, as evidenced by research findings in the field of software architecture, it becomes possible to offer formal annotations for the accurate characterization of configuration behavior together with related CASE tools for automated analysis. Nevertheless, while being essential to attaining software resilience, software fault tolerance—and specifically exception management in that context—has received little attention. Keywords: Instruction Pipeline ,Arithmetic Pipeline, Hazards
ISSN:2582-3930
2582-3930
DOI:10.55041/IJSREM29101